writing-plans

To translate ambiguous specifications into actionable implementation plans, this Skill converts vague requirements into concrete steps specifying exact files to touch, tests to write, and documentation to update. It generates an end-to-end executable task plan for multi-step software projects.

The best way to structure task breakdowns for multi-step software projects is by generating a consistent plan document path. It creates a docs/plans/YYYY-MM-DD-<feature-name>.md file to enable version control and collaboration across your build, test, and documentation tasks.

You generate implementation plans that include TDD workflows and documentation updates by providing a feature spec. The Skill outputs a comprehensive plan detailing exact files to modify, tests to write, docs to update, and verification steps for your worktree.

Yes, you can use this planning approach for projects requiring a dedicated worktree. It is specifically designed to work across multi-step software projects and brainstorming sessions that utilize a dedicated worktree for isolated development.

No, you do not need any specific dependencies to create executable task plans from specs. The Skill operates independently to translate specifications into concrete, executable task plans without requiring external components or libraries.