Workflow Orchestration

Enter plan mode for every non-trivial task. Do not start implementation without a plan.
If something goes sideways: STOP and re-plan immediately. Do not keep pushing.
Use plan mode for verification steps as well as building.
Write detailed specs upfront to reduce ambiguity (inputs, outputs, edge cases, success criteria).

Use subagents liberally to keep the main context window clean.
Offload research, exploration, and parallel analysis to subagents.
For complex problems, use more compute via subagents (e.g. multiple agents in parallel where appropriate).
One task per subagent for focused execution; give clear, self-contained instructions.

After ANY correction from the user: update tasks/lessons.md with the pattern.
Write rules for yourself that prevent the same mistake.
Iterate on these lessons until mistake rate drops.
Review lessons at session start for the relevant project.

For non-trivial changes: pause and ask "Is there a more elegant way?"
If a fix feels hacky: "Knowing everything I know now, implement the elegant solution."
Skip for simple, obvious fixes; do not over-engineer.
Challenge your own work before presenting it.

Practice	Action
Plan first	Write plan to `tasks/todo.md` with checkable items
Verify plan	Check in before starting implementation
Track progress	Mark items complete as you go
Explain changes	High-level summary at each step
Document results	Add review section to `tasks/todo.md`
Capture lessons	Update `tasks/lessons.md` after corrections

Simplicity first: Make every change as simple as possible. Impact minimal code.
No laziness: Find root causes. No temporary fixes. Senior developer standards.
Minimal impact: Changes touch only what is necessary. Avoid introducing new bugs.

Enter plan mode for every non-trivial task. Do not start implementation without a plan.
If something goes sideways: STOP and re-plan immediately. Do not keep pushing.
Use plan mode for verification steps as well as building.
Write detailed specs upfront to reduce ambiguity (inputs, outputs, edge cases, success criteria).

Use subagents liberally to keep the main context window clean.
Offload research, exploration, and parallel analysis to subagents.
For complex problems, use more compute via subagents (e.g. multiple agents in parallel where appropriate).
One task per subagent for focused execution; give clear, self-contained instructions.

After ANY correction from the user: update tasks/lessons.md with the pattern.
Write rules for yourself that prevent the same mistake.
Iterate on these lessons until mistake rate drops.
Review lessons at session start for the relevant project.

For non-trivial changes: pause and ask "Is there a more elegant way?"
If a fix feels hacky: "Knowing everything I know now, implement the elegant solution."
Skip for simple, obvious fixes; do not over-engineer.
Challenge your own work before presenting it.

Practice	Action
Plan first	Write plan to `tasks/todo.md` with checkable items
Verify plan	Check in before starting implementation
Track progress	Mark items complete as you go
Explain changes	High-level summary at each step
Document results	Add review section to `tasks/todo.md`
Capture lessons	Update `tasks/lessons.md` after corrections

Simplicity first: Make every change as simple as possible. Impact minimal code.
No laziness: Find root causes. No temporary fixes. Senior developer standards.
Minimal impact: Changes touch only what is necessary. Avoid introducing new bugs.