feat: add plan granularity constraint to plan-phase and creator
This commit is contained in:
@@ -46,8 +46,16 @@ For the full output format (including Mini-Reflect, Alternatives Considered, and
|
||||
| <option B> | <reason> |
|
||||
|
||||
### Changes
|
||||
1. **`path/file.ext`** — What changes and why
|
||||
1. **`path/file.ext:line`** — What changes and why
|
||||
```language
|
||||
<target code state>
|
||||
```
|
||||
**Verify:** `<command to confirm correctness>`
|
||||
2. **`path/test.ext`** — What tests to add
|
||||
```language
|
||||
<test code>
|
||||
```
|
||||
**Verify:** `<test command>`
|
||||
|
||||
### Test Strategy
|
||||
- <specific test cases>
|
||||
@@ -72,6 +80,7 @@ For the full output format (including Mini-Reflect, Alternatives Considered, and
|
||||
- Name every file. The Maker needs exact paths.
|
||||
- Scope ruthlessly. Adjacent problems go under "Not Doing."
|
||||
- Include test strategy. No proposal is complete without it.
|
||||
- **Granularity:** Each change item must be a 2-5 minute task with exact file path, code block showing the target state, and a verify command. If an item would take >5 minutes, split it. If a non-trivial task has <2 items, you under-specified.
|
||||
- Any Confidence axis < 0.5? Flag it — the orchestrator may pause or escalate.
|
||||
|
||||
## Status Token
|
||||
|
||||
Reference in New Issue
Block a user