القائمة
Project milestone verification and rollback patterns. Use when designing verify sections, rollback procedures, or testing strategies for project milestones.
التثبيت باستخدام 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-planning-verification |
| description | Project milestone verification and rollback patterns. Use when designing verify sections, rollback procedures, or testing strategies for project milestones. |
NEVER defer all testing to a final milestone. Each milestone owns its own assertions.
Verify sections must include assertions to add to molecule scenarios, proving the milestone completed successfully.
Every feature milestone MUST include an implementation pattern note specifying: which task file to create, which plays to add to site.yml, which tags to use, and which molecule scenario to create. NEVER leave "how it integrates" as an open question.
Feature milestones MUST reference the relevant skills by name so implementers know which skills to load.
Rollback MUST fully restore the baseline state, including auth credentials and connection methods. If a milestone changes how Ansible connects to a target (e.g., password → key auth), the rollback MUST reverse the connection method too.
When a milestone changes the auth/connection method for a dynamic group, the plan MUST specify how subsequent plays and per-feature scenarios detect and adapt to the new auth method.
Every rollback section must undo EVERYTHING the milestone changed. Check: UCI config, packages, files, auth state, cron jobs, service enablement. A partial rollback leaves the system in an undefined state.
Per the project's "Bake, don't configure at runtime" principle: every package belongs in the image build, NOT at runtime. If a plan proposes opkg install or apt install during converge, reject it. Configure roles only do host-specific topology changes.
Rollback tags must be clearly defined. Use --tags <feature>-rollback pattern for consistent rollback execution.
Every plan MUST include a Testing Strategy section with:
molecule/defaultBefore execution, ALWAYS run the plan through the Plan Review Checklist against all referenced skills. Previous bug: the OpenWrt router plan had two critical issues (SSH auth transition, dynamic group persistence) that would have broken implementation — both caught only by cross-referencing skills during review.
test.env.generated (test) or .env.generated (production)Manual testing milestones verify by EXECUTION — not by confirming a file exists. The verify section MUST require "All N sections of Playbook X executed and passed on real hardware" with specific outcomes for key interactions. NEVER use "verify Playbook exists" as a criterion.
The project plan's reference to the playbook MUST include: file path, section numbers, sub-section count, and explicit "EXECUTE" language. NEVER say "walkthrough," "review," or passive voice.
For HOW to write the playbook itself (exhaustive feature enumeration,
per-app steps, host-awareness, error cases), see the
manual-testing-playbook-writing skill.