LucasSantana-Dev Plan Change
Restate the task, identify the minimum files involved, produce an ordered plan, and define how to verify each step.
Steps
- Restate the task — one sentence, no ambiguity
- Identify files — minimum set of files and systems involved
- Sequence the plan — ordered steps with dependencies marked
- Set verification — what command or check proves each step worked
- Flag risks — ambiguity, side effects, or unknowns before editing
Output
Task: <one-sentence restatement>
Files: <file list>
Plan: 1. <step> → verify: <check>
2. <step> → verify: <check>
Risks: <list or none>
Rules
- Never jump into implementation if the request is ambiguous
- Never produce a huge abstract plan for a small task
- Include verification criteria for each meaningful step
- Call out risks before editing, not after