writing-plans

Start with a header stating goal, architecture, and tech stack, then break the work into tasks of 2-5 minutes each. Every task lists exact files, a failing test, minimal implementation, run commands with expected output, and a commit step.

Each task should represent 2-5 minutes of focused work, such as writing one failing test or adding one small function. Large items like 'build authentication' should be split into separate tasks for the model, hashing utility, and tests.

Yes. The skill recommends planning even for solo or simple-seeming work, because assumptions cause bugs and documentation helps future you. A good plan makes implementation obvious without guessing.

Common mistakes include vague tasks, incomplete code snippets, missing verification steps, and unspecified file paths. Each task needs copy-pasteable code, exact commands with expected output, and precise paths like src/models/user.py.

The skill argues plans should rarely be skipped, but they are designed for multi-step features and subagent delegation. Trivial one-line changes may not justify the full plan structure with TDD cycles and commit steps.