writing-plans

Convert specifications into test-driven implementation plans with exact file paths and commands.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/jacexh/skills --skill writing-plans-jacexh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/jacexh/skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/jacexh/skills --skill writing-plans-jacexh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a specification or requirements document into a complete, unambiguous implementation plan that a developer with no prior project context can follow. Remove uncertainty about which files to change, what tests to write, how to run them, and how to commit incremental progress.

Core Features & Use Cases

  • TDD-first task decomposition: Break features into 2–5 minute steps such as write failing test, run to fail, implement minimal code, run to pass, and commit.
  • Precise, actionable output: Provide exact file paths, test and code snippets, expected commands and outputs, and the canonical plan document header and save location.
  • Execution handoff guidance: Offer clear handoff options including subagent-driven development or a parallel session using an executing-plans sub-skill, and note required sub-skills when appropriate.

Quick Start

Generate a step-by-step implementation plan from the given specification and 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 feature specifications into test-driven implementation plans?

To break feature specifications into test-driven implementation plans, decompose requirements into 2–5 minute TDD cycles. Each step includes writing a failing test, running it, implementing minimal code, passing the test, and committing the incremental progress.

What is the best way to create bite-sized development tasks for engineers with no project context?

Creating bite-sized development tasks for engineers with no project context involves generating unambiguous steps with exact file paths, test and code snippets, expected commands, and commit instructions. This removes uncertainty about modifications and verifications.

How do I generate TDD workflows for worktree-based execution?

To generate TDD workflows for worktree-based execution, produce a plan document with a canonical header and save location, such as docs/plans/YYYY-MM-DD-feature-name.md. This structure supports parallel sessions and subagent-driven development.

Can I use task breakdown for bug fixes and architecture changes?

Yes, you can use task breakdown for bug fixes and architecture changes. The planning mechanism applies test-driven step-by-step decomposition to any specification, ensuring quick verifiable actions regardless of the modification type.

Does implementation planning require prior knowledge of the codebase structure?

Implementation planning does not require prior codebase knowledge. It translates specifications into precise, actionable outputs including exact file paths and snippets, enabling developers with no project context to execute tasks verifiable quickly.