commit pi sessions
This commit is contained in:
@@ -1,2 +1,18 @@
|
||||
Break the following request into a numbered plan with concrete file paths and
|
||||
acceptance criteria. Do not implement until I approve.
|
||||
---
|
||||
description: Create a structured implementation plan before coding
|
||||
argument-hint: "[task or feature]"
|
||||
subagent: true
|
||||
fork: true
|
||||
---
|
||||
Create a structured implementation plan for: $@
|
||||
|
||||
Follow this format:
|
||||
1. **Goal** — one-sentence objective
|
||||
2. **Constraints** — existing code, dependencies, tests, or assumptions to respect
|
||||
3. **Approach** — high-level strategy and rationale
|
||||
4. **Steps** — numbered, actionable tasks small enough to verify one at a time
|
||||
5. **Verification** — how to confirm each step works (tests, logs, manual checks)
|
||||
6. **Risks & Rollbacks** — what could go wrong and how to undo safely
|
||||
7. **Open Questions** — anything that needs clarification before starting
|
||||
|
||||
Use the codebase context as needed. Do not write implementation code yet; only produce the plan.
|
||||
Reference in New Issue
Block a user