Generate detailed implementation plans with exact file paths and test commands.
npx skills add https://github.com/obra/clank --skill writing-plans
Please help me install this Agent Skill. Skill: Writing Plans Source: https://github.com/obra/clank/tree/main/skills/collaboration/writing-plans Command: npx skills add https://github.com/obra/clank --skill writing-plans
Handoffs between design and implementation, or between developers, often suffer from incomplete or ambiguous plans. This skill ensures the creation of highly detailed, bite-sized implementation plans that can be executed by any engineer, even with zero prior codebase context, minimizing confusion and rework.
"I'm using the Writing Plans skill to create the implementation plan."
docs/plans/YYYY-MM-DD-<feature-name>.md.High-intent search queries and answers about installing and using this skill.
Implementation plans decompose features into atomic steps with exact file paths, code snippets, and commands. Create a Markdown file in docs/plans/ specifying each task (2-5 minutes each), including testing and commit actions, so any engineer can execute without prior codebase context.
A comprehensive plan specifies exact file paths, complete code snippets, test scaffolds, documentation checks, and step-by-step instructions aligned with DRY, YAGNI, and TDD principles. It assumes zero prior knowledge of the codebase or toolset.
Generate implementation plans after design approval and before development starts. They bridge the handoff between design and implementation, ensuring bite-sized, actionable tasks that minimize confusion and rework across team members.
Yes. Plans are structured with explicit file paths, code, and commands, making them executable by AI agents or another developer. The zero-context assumption ensures any executor—human or automated—can complete tasks independently.
Breaking features into 2-5 minute atomic steps with precise commands and expected outputs reduces ambiguity. Each step includes testing and commit actions, enabling parallel execution or handoff without clarification rounds.
A design document defines what to build and why; an implementation plan specifies exactly how with file paths, code snippets, and sequential commands. Plans assume zero codebase knowledge and are executable, not conceptual.
byonk19-svgConduct a structured discovery interview to produce a design brief.
blakesimsValidate feature branch merge readiness with integration checks and summaries.
nextlwCreate NexAgent tools with standardized structure, validation, and TOON documentation.
cabeznoConverts requirements into actionable implementation plans with file paths and TDD steps.