45 lines
1.1 KiB
Markdown
45 lines
1.1 KiB
Markdown
# Planning Gate
|
|
|
|
A coding agent must complete this gate before writing an implementation plan.
|
|
|
|
## Required Output
|
|
|
|
```md
|
|
## Project Context Loaded
|
|
|
|
Read:
|
|
- {file path}
|
|
|
|
Relevant understanding:
|
|
- Project goal:
|
|
- Current focus:
|
|
- Active constraints:
|
|
- Decisions affecting this task:
|
|
- Evidence, reflections, or commitments affecting this task:
|
|
- Files or modules likely involved:
|
|
- Unknowns, stale docs, or conflicts:
|
|
|
|
Gate result:
|
|
- Passed or Blocked
|
|
```
|
|
|
|
## Pass Criteria
|
|
|
|
The gate passes only when:
|
|
|
|
- required documents were read
|
|
- `memory-index.md` was checked when present
|
|
- task-relevant decisions were checked
|
|
- relevant evidence, reflection, and commitment indexes were checked when applicable
|
|
- stale or conflicting docs were called out
|
|
- the plan respects project positioning and constraints
|
|
|
|
## Block Criteria
|
|
|
|
Block planning when:
|
|
|
|
- required documents are missing and cannot be inferred
|
|
- current state conflicts with the user request
|
|
- an existing decision appears to be violated
|
|
- the task changes project positioning or architecture without human confirmation
|