writing-plans

Generate test-first implementation plans with exact file paths and code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns high-level specifications into actionable, test-first implementation plans so engineers can implement features reliably without prior project context, preventing ambiguous or incomplete task handoffs.

Core Features & Use Cases

  • Breaks a spec into focused, 2–5 minute tasks that follow RED-GREEN-REFACTOR and frequent commits.
  • Specifies exact file paths to create or modify, complete test and implementation code for each step, run commands with expected outputs, and commit instructions.
  • Enforces no-placeholders, self-review checks, and plan header conventions; ideal for handing work to subagents or junior engineers in a new worktree.

Quick Start

Create a complete, test-first implementation plan from the spec and save it to docs/cadence/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 generate a test-driven implementation plan from a specification?

This Skill generates test-driven implementation plans by breaking specifications into 2-5 minute tasks with complete test code, exact file paths, and expected command outputs, ensuring no placeholders are left in the final document.

What is the best way to break down a multi-step software development feature into bite-sized tasks?

Breaking down multi-step features involves creating test-first plans with per-task commits in a dedicated worktree, specifying exact file edits, runnable commands, and complete implementation code for each 2-5 minute step.

Can I hand off an implementation plan to a junior engineer without prior project context?

Yes, implementation plans are designed for handoffs to junior engineers or subagents without prior project context, enforcing no-placeholders and self-review checks while providing complete test and implementation code for every step.

Does the generated plan include exact file paths and complete test code for each step?

Yes, the generated plan includes exact file paths, complete test and implementation code, runnable commands with expected outputs, and commit instructions for each step, strictly enforcing a no-placeholders rule.

How do I save an implementation plan to the correct file path in my repository?

You save an implementation plan by having the Skill write the test-first task breakdown directly to docs/cadence/plans/YYYY-MM-DD-<feature-name>.md, ensuring the file path follows the required plan header conventions.

What are the limitations of using a worktree for task decomposition in test-driven development?

The approach is limited to multi-step software development features where a dedicated worktree is used, making it unsuitable for trivial single-file edits or projects that do not follow test-driven development workflows.