writing-plans

To create an implementation plan from specs, decompose requirements into bite-sized tasks covering file touchpoints, test scaffolding, and version-controlled commits. This ensures engineers can code with zero context by documenting every necessary file, test, and documentation check.

An implementation plan for zero-context engineers must include specific file touchpoints, test scaffolding instructions, documentation references, and frequent version-controlled commits. It decomposes tasks end-to-end so developers can execute without prior knowledge of the codebase.

Break down features into bite-sized tasks by mapping each step to specific file modifications, test scaffolding, and frequent version-controlled commits. This approach satisfies DRY and YAGNI principles while providing end-to-end guidance across code, tests, and docs.

Yes, you can generate test scaffolding and commit strategies within a software implementation plan. The plan format explicitly integrates testing requirements and frequent version-controlled commits alongside file touchpoints and documentation checks for each decomposed task.

Yes, the writing-plans skill is designed to run in a dedicated git worktree environment, typically created during brainstorming. It saves the generated implementation plans directly to the docs/plans directory using a YYYY-MM-DD-<feature-name>.md format.

The best way to document file touchpoints and testing requirements is creating a comprehensive implementation plan. It maps each task to exact files, details testing procedures, references necessary documentation, and structures outputs as a repeatable markdown file.