|
| 1 | +## Workflow Orchestration |
| 2 | + |
| 3 | +### 1. Plan Mode Default |
| 4 | + |
| 5 | +- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions) |
| 6 | +- If something goes sideways, STOP and re-plan immediately - don't keep pushing |
| 7 | +- Use plan mode for verification steps, not just building |
| 8 | +- Write detailed specs upfront to reduce ambiguity |
| 9 | + |
| 10 | +### 2. Subagent Strategy |
| 11 | + |
| 12 | +- Use subagents liberally to keep main context window clean |
| 13 | +- Offload research, exploration, and parallel analysis to subagents |
| 14 | +- For complex problems, throw more compute at it via subagents |
| 15 | +- One task per subagent for focused execution |
| 16 | + |
| 17 | +### 3. Self-Improvement Loop |
| 18 | + |
| 19 | +- After ANY correction from the user: update tasks/lessons-md\* with the pattern |
| 20 | +- Write rules for yourself that prevent the same mistake |
| 21 | +- Ruthlessly iterate on these lessons until mistake rate drops |
| 22 | +- Review lessons at session start for relevant project |
| 23 | + |
| 24 | +### 4. Verification Before Done |
| 25 | + |
| 26 | +- Never mark a task complete without proving it works |
| 27 | +- Diff behavior between main and your changes when relevant |
| 28 | +- Ask yourself: "Would a staff engineer approve this?" |
| 29 | +- Run tests, check logs, demonstrate correctness |
| 30 | + |
| 31 | +### 5. Demand Elegance (Balanced) |
| 32 | + |
| 33 | +- For non-trivial changes: pause and ask "is there a more elegant way?" |
| 34 | +- If a fix feels hacky: "Knowing everything I know now, implement the elegant solution" |
| 35 | +- Skip this for simple, obvious fixes - don't over-engineer |
| 36 | +- Challenge your own work before presenting it |
| 37 | + |
| 38 | +### 6. Autonomous Bug Fixing |
| 39 | + |
| 40 | +- When given a bug report: just fix it. Don't ask for hand-holding |
| 41 | +- Point at logs, errors, failing tests - then resolve them |
| 42 | +- Zero context switching required from the user |
| 43 | +- Go fix failing CI tests without being told how |
| 44 | + |
| 45 | +## Task Management |
| 46 | + |
| 47 | +1. **Plan First**: Write plan to 'tasks/todo.md with checkable items |
| 48 | +2. **Verify Plan**: Check in before starting implementation |
| 49 | +3. **Track Progress**: Mark items complete as you go |
| 50 | +4. **Explain Changes**: High-level summary at each step |
| 51 | +5. **Document Results**: Add review section to 'tasks/todo.md\* |
| 52 | +6. **Capture Lessons**: Update 'tasks/lessons.md after corrections |
| 53 | + |
| 54 | +## Core Principles |
| 55 | + |
| 56 | +- **Simplicity First**: Make every change as simple as possible. Impact minimal code. |
| 57 | +- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards. |
| 58 | +- **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs. |
0 commit comments