planning

Convert design.md and requirements.md into an executable implementation plan with dependencies and approval.

Updated Mar 29, 2026

Search Tags:#workflow #planning #tdd #dependency-management #task-decomposition #implementation-plan

Ready to run

npx skills add https://github.com/sizukutamago/claude-code-harness --skill planning-sizukutamago

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/sizukutamago/claude-code-harness/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/sizukutamago/claude-code-harness --skill planning-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents ad‑hoc implementations by converting an approved design and requirements into a clear, testable implementation plan so teams avoid hidden dependencies, wasted work, and late surprises.

Core Features & Use Cases

Task decomposition: Break a design into TDD-sized tasks that can be implemented and tested independently.
Dependency & order resolution: Identify task dependencies, determine execution order, and mark parallelizable work.
Review and approval workflow: Produce a plan.md, dispatch automated reviewers, capture human approval, and iterate until the plan is acceptable.
Use Case: Prepare an implementation plan for a multi-file feature, ensuring repository-level TDD readiness and minimizing integration risk.

Quick Start

Use the planning skill with an approved design.md and its requirements.md to generate docs/plans/{slug}-plan.md listing tasks, dependencies, completion criteria, and a request for human approval.

Frequently Asked Questions about planning

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

FAQPage Schema

How do I break down a design document into TDD-sized implementation tasks?▼

To break down a design document into TDD-sized tasks, decompose approved requirements into a sequenced set of implementation steps, identify dependencies, and mark parallelizable groups. This produces an executable plan document with explicit completion criteria.

What is the best way to resolve task dependencies and implementation order for a multi-file feature?▼

Resolving task dependencies for a multi-file feature involves analyzing design requirements to determine execution order and highlighting parallelizable work. This minimizes integration risk and ensures repository-level TDD readiness.

Do I need approved design and requirements documents to generate an implementation plan?▼

Yes, you need approved design and requirements documents to generate an implementation plan. The planning process requires a design.md and requirements.md file to decompose features and determine the implementation order.

How does the implementation plan approval workflow handle iterations and human confirmation?▼

The implementation plan approval workflow dispatches automated reviewers, captures human confirmation for requirement selection, and iterates based on feedback. It continues refining the plan document until final human approval is achieved.

What should be included in an executable plan document to prevent ad-hoc implementations?▼

An executable plan document should include task listings with dependencies, parallelizable groups, explicit completion criteria, and risk notes. This prevents ad-hoc implementations by ensuring testable tasks and minimizing late surprises.