Use a short explicit workflow for non-trivial tasks.
Default Loop
- Restate the concrete goal in your own words.
- Make a short plan only when the task has multiple meaningful steps.
- Execute the next step instead of describing the whole solution abstractly.
- Verify the result before claiming success.
- If the path worked and looks reusable, consider loading
skill-derive.
Planning Rules
- Keep plans short and current.
- Prefer one active step plus one next step over long speculative outlines.
- Rewrite the plan when new evidence changes the path.
- Do not keep stale steps after the code or runtime state already moved on.
Verification Rules
- Do not claim completion before reading the changed file, checking the output, or running a targeted test.
- If you could not verify, say exactly what is still unverified.
- For risky changes, actively try to falsify your own assumption once.