writing-plans

Generates detailed multi-task implementation plans with TDD steps from a spec.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill writing-plans-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/writing-plans
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill writing-plans-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: tasks end up too vague, placeholders slip in, and engineers without codebase context get stuck. This Skill produces a complete, bite-sized implementation plan that an engineer with zero project context can execute task by task. ## Core Features & Use Cases - Structured Plan Documents: Generates plans saved to docs/plans/YYYY-MM-DD-<feature-name>.md with a mandatory header covering goal, architecture, tech stack, and global constraints. - Bite-Sized TDD Tasks: Breaks work into tasks with exact file paths, interface contracts (consumes/produces), and 2-5 minute steps following a write-failing-test, implement, verify, commit cycle. - Placeholder Prevention & Self-Review: Enforces complete code in every step and runs a self-review checklist for spec coverage, placeholder scans, and type consistency across tasks. - Use Case: Given a feature spec for a new API endpoint, produce a plan where each task lists exact files to create or modify, full test and implementation code, run commands with expected output, and commit commands, then hand off to delegated or inline execution. ## Quick Start Ask the agent to use the writing-plans skill to turn your spec into a step-by-step TDD implementation plan saved under docs/plans.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an implementation plan from a spec?

Start with a header covering goal, architecture, tech stack, and global constraints, then decompose the work into tasks with exact file paths and interface contracts. Each task contains bite-sized TDD steps: write the failing test, verify it fails, implement, verify it passes, and commit.

How granular should tasks be in an implementation plan?

Each step should be one action taking 2-5 minutes, such as writing a single failing test or running it. Tasks themselves are the smallest unit carrying their own test cycle, ending with an independently testable deliverable a reviewer could approve or reject on its own.

What makes an implementation plan fail during execution?

Plans fail when they contain placeholders like TODO or 'add appropriate error handling', reference undefined types or functions, or lack exact file paths and complete code. A self-review pass checking spec coverage, placeholder patterns, and cross-task type consistency catches these issues.

When should a spec be split into multiple implementation plans?

Split when the spec covers multiple independent subsystems that should have been separated during brainstorming. Each plan should produce working, testable software on its own rather than depending on sibling plans to function.

Where should implementation plan documents be saved?

Plans are saved to docs/plans/YYYY-MM-DD-<feature-name>.md by default. User preferences for plan location override this default, and the plan filename is referenced again during the execution handoff step.