uv-writing-plans
Writing Plans
Overview
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Where the plan lives (planning-with-files style): write the plan to task_plan.md in the target project root (not inside this pkb repo). Use task_plan.md as the single durable tracker by keeping these sections up to date:
## Findings / notes— decisions and discoveries worth keeping## Progress log— what you did + evidence (commands, outputs)## Errors encountered— failure → attempt → fix/next step
Use the templates in:
productivity/writing-plans/references/task_plan.md