docs: structure planning and execution state
This commit is contained in:
@@ -10,6 +10,8 @@ Create or update an execution-ready plan for: $ARGUMENTS
|
||||
2. Use `researcher`, `explorer`, and `reviewer` as needed.
|
||||
3. Write the canonical plan to basic-memory under `plans/<slug>`.
|
||||
4. Include: objective, scope, assumptions, constraints, task breakdown, parallel lanes, verification oracle, risks, and open findings.
|
||||
5. Set `Status: approved` only when `builder` can execute the plan without guesswork. Otherwise leave it blocked and explain why.
|
||||
5. When parallelization or phased verification matters, define intended lanes with claimed files/areas, inter-lane dependencies, and verification intent (including `smoke` vs `full` mode where the distinction affects execution).
|
||||
6. Ensure the plan gives builder enough information to create the structured `executions/<slug>` note without guessing lane ownership, claimed areas, or verification expectations.
|
||||
7. Set `Status: approved` only when `builder` can execute the plan without guesswork. Otherwise leave it blocked and explain why.
|
||||
|
||||
Return the plan slug and the key execution checkpoints.
|
||||
|
||||
Reference in New Issue
Block a user