Decompose design docs into execution-ready subtasks with commands and outputs.
npx skills add https://github.com/CityBear3/dotfiles --skill create-plan-citybear3
Please help me install this Agent Skill. Skill: create-plan Source: https://github.com/CityBear3/dotfiles/tree/main/claude/skills/create-plan Command: npx skills add https://github.com/CityBear3/dotfiles --skill create-plan-citybear3
It prevents ambiguous engineering work by decomposing a design doc or clear scope into small, independently verifiable tasks that an agent team can execute without extra context.
Use the create-plan skill to generate a self-contained implementation plan for your approved Design Doc by invoking /create-plan during the planning phase.
High-intent search queries and answers about installing and using this skill.
Implementation planning decomposes a design doc into small, independently verifiable tasks with exact file paths, concrete commands, and expected outputs. This creates self-contained plans requiring no extra context for agent teams to execute.
TDD-aligned task decomposition forces behavior-changing tasks to follow red, green, refactor discipline with pinned verification per task. This ensures each work unit is independently testable and commit-ready before moving forward.
Self-contained implementation plans are generated by specifying explicit affected files, concrete step instructions including exact commands, and expected outputs. Plans are saved to a configured directory like docs/plans for safe storage.
Implementation planning applies directly to autonomous engineering work handed off to agent teams. It prevents ambiguous work by producing bite-sized, verifiable units designed to be independently testable and commit-ready.
Engineering documentation plans are saved to docs/plans/YYYY-MM-DD-feature-name.md unless overridden by existing conventions. This ensures safe planning storage and easy retrieval for subsequent implementation phases.
Task decomposition for autonomous agents is not suitable for vaguely scoped tasks lacking a design doc. It requires clearly defined scope to produce verifiable, execution-ready subtasks with explicit affected files and concrete commands.
m2ai-portfolioRequire requirements, design, and task decomposition documents before code generation.
kkestellExecute repository implementation plans with code changes, tests, and reviews.
ourskyPlan and execute Git commits from staged changes in dependency order.
edlngGenerate test-driven implementation plans with file paths and self-review checklists.
