Atomic plan format and QA contract shared by planning and execution skills. Use when generating, validating, or executing plans with Phase 0, baseline evidence, and final QA loops.
Shared rules for atomic plan formatting, Phase 0 requirements, baseline evidence, and final QA loops.
### Phase N — <Title>.- [ ] [P#-T#] or - [x] [P#-T#].Phase 0 must:
policy-compliance-order,evidence-and-timestamp-conventions.Baseline command-step artifacts must include:
Timestamp:Command:EXIT_CODE:Output Summary:For plans that change code or tests, the final QA phase must run the applicable toolchain loop in order:
If any step fails or changes files, restart from step 1 until the final pass is clean.
minor-audit plans must include:
They must not depend on spec.md or user-story.md when those documents are intentionally absent.
Any regression-test task expected to fail before a later fix must:
[expect-fail] tag in the task title,Use these exact signals for executor preflight validation:
PREFLIGHT: ALL CLEARPREFLIGHT: REVISIONS REQUIRED