68 lines
2.3 KiB
Markdown
68 lines
2.3 KiB
Markdown
# Planning Gate
|
|
|
|
A coding agent must complete this gate after the repository-local Concurrent Worktree Check and before writing an implementation plan.
|
|
|
|
## Peer Scope Check
|
|
|
|
Use `git worktree list --porcelain` to identify other local worktrees. When an available peer task record or committed branch diff is relevant, use its scope and promotion candidates to assess overlap.
|
|
|
|
Do not inspect or modify arbitrary uncommitted files in another task's worktree. A missing peer task record is not itself a blocker, but unresolved overlap that could change the plan is. Code-path overlap alone is a warning. Block when semantic decisions conflict or overlapping unknown changes cannot be preserved safely.
|
|
|
|
## Required Output
|
|
|
|
```md
|
|
## Project Context Loaded
|
|
|
|
Task context:
|
|
- Task record, if any:
|
|
- Mode, if applicable:
|
|
- Branch:
|
|
- Worktree:
|
|
- Base commit:
|
|
- Existing changes:
|
|
- Other relevant local worktrees:
|
|
- Overlap or semantic-conflict assessment:
|
|
|
|
Read:
|
|
- {file path}
|
|
|
|
Relevant understanding:
|
|
- Project goal:
|
|
- Current integrated focus:
|
|
- Active task scope:
|
|
- 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:
|
|
|
|
- current branch, worktree, base commit, status, and task scope are resolved
|
|
- the active task record exists for repository-changing work and matches the current scope
|
|
- required documents were read
|
|
- task-relevant decisions were checked
|
|
- relevant evidence, reflection, and commitment indexes were checked when applicable
|
|
- other active local task scopes were assessed
|
|
- stale, unknown, or conflicting context was called out
|
|
- the plan respects project positioning and constraints
|
|
|
|
## Block Criteria
|
|
|
|
Block planning when:
|
|
|
|
- the intended branch or worktree is unresolved
|
|
- existing overlapping changes cannot be attributed or preserved safely
|
|
- required worktree isolation failed or later operations cannot remain rooted there
|
|
- required documents are missing or a concurrency upgrade is incomplete
|
|
- current integrated state conflicts with the user request
|
|
- an existing decision appears to be violated
|
|
- semantic decisions conflict across active tasks
|
|
- the task changes project positioning or architecture without human confirmation
|