writing-plans

Produce detailed implementation plans with tasks, dependencies, and artifacts.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill writing-plans-oduffy-delphi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/oduffy-delphi/coordinator-claude/tree/main/plugins/coordinator/skills/writing-plans
Command: npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill writing-plans-oduffy-delphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear and actionable planning is often the bottleneck in software projects. This skill guides teams to break work into executable tasks with defined inputs, outputs, and dependencies, reducing ambiguity and improving delivery confidence.

Core Features & Use Cases

  • Decompose features into bounded tasks with explicit dependencies and estimates
  • Map each task to required files, tests, docs, and review steps
  • Align planning with iterative delivery and TDD for reliable progress

Quick Start

Describe a feature as a plan with tasks, files, tests, and reviews, then save it to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down vague software features into actionable implementation plans?

Implementation plans translate high-level requirements into explicit tasks with defined inputs, outputs, dependencies, and estimates. This decomposition reduces ambiguity by mapping each bounded task to required files, tests, and documentation for reliable execution.

What is the best way to map feature tasks to required files and tests?

Mapping feature tasks involves aligning planning with iterative delivery and test-driven development. You describe the feature, decompose it into bounded tasks with explicit dependencies, and map each step to required files, tests, docs, and review checkpoints.

How do I save an implementation plan for repeatable execution across a team?

You save the implementation plan in a standardized location using the format docs/plans/YYYY-MM-DD-<feature-name>.md. This ensures the decomposed tasks, dependencies, and required artifacts are stored consistently for repeatable team execution.

Does task decomposition in project management help reduce delivery ambiguity?

Task decomposition reduces delivery ambiguity by breaking features into bounded tasks with explicit dependencies and estimates. This clear and actionable planning approach guides teams to define executable tasks, improving overall delivery confidence.

Can I align implementation plans with test-driven development methodologies?

Yes, implementation plans align directly with test-driven development by mapping each task to required files and tests before execution. This iterative delivery approach ensures reliable progress through defined task boundaries and explicit dependencies.