القائمة
Review checklist for project plans before execution. Includes structural validation, container/VM requirements, cross-reference checks, and performance considerations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Project architecture and design principles for vm_builds Ansible project. Includes bake vs configure patterns, two-role service model, and deployment lifecycle.
Python code conventions. Functions return errors, .env parsing strips quotes, type hints required.
Proactive validation patterns to catch issues early, prevent debugging blind, and establish testing habits before problems escalate.
Update skills and rules when encountering new issues to prevent recurrence. Includes hard-fail patterns, code custodianship, and mandatory testing requirements.
LXC container provisioning and configuration patterns. Use when creating LXC services, managing container networking, or handling LXC template operations.
Molecule test performance optimization patterns. Template caching, NTP sync, pct_remote overhead, apt cache, selective rebuilds.
| name | project-plan-review |
| description | Review checklist for project plans before execution. Includes structural validation, container/VM requirements, cross-reference checks, and performance considerations. |
Use when editing or reviewing project plans in docs/projects/ to ensure completeness, correctness, and prevent common planning mistakes.
proxmox_lxc_default_template - create service-specific template varsplaybooks/cleanup.yml for all featuresStructural validation:
# Dynamic group reconstruction pattern
- name: Reconstruct dynamic group for rollback
include_tasks: tasks/reconstruct_service_group.yml
# Auth transition specification
# Play ordering: SSH key → API token → configure with new auth method
# Detection: verify new auth method before removing old
# Rollback: reverse order of transition
Cross-reference verification:
# Check these exist before completing plan:
- grep for VMID in group_vars/all.yml
- grep for flavor group in inventory/hosts.yml
- grep for platform in molecule/*/molecule.yml
- grep for cleanup in both cleanup playbooks
- grep for verify assertions in molecule/default/verify.yml
Container IP allocation check:
# Verify offset doesn't collide with existing allocations:
# Current: WG=3, Pi-hole=10, rsyslog=12, HA=14, Jellyfin=15,
# Kodi=16, Moonlight=17, Gaming=18, Kiosk=19, Netdata=21
# WAN hosts use NAT bridge (10.99.x.x) — offsets just need to
# be unique per host. No host IP collision risk.
NEVER explain what project plans are in review rules NEVER keep blocked milestones as stubs in current project NEVER omit LXC features declaration (nesting=1, privileged, etc.) NEVER skip image build milestone - configure roles can't install packages