writing-plans

Generate executable implementation plans from feature specs with TDD steps.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/Jackliu-miaozi/murmur-protocol --skill writing-plans-jackliu-miaozi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Jackliu-miaozi/murmur-protocol/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/Jackliu-miaozi/murmur-protocol --skill writing-plans-jackliu-miaozi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a concrete, executable plan before coding. This Skill generates comprehensive implementation plans from a spec, ensuring nothing important is missed and all steps are traceable.

Core Features & Use Cases

  • End-to-end planning: Create step-by-step tasks covering files, tests, docs, and commits.
  • TDD-aligned workflows: Emphasizes red/green/refactor cycles and frequent commits.
  • Documentation-driven execution: Plans saved as docs/plans/YYYY-MM-DD-<feature-name>.md for traceability.
  • Use Case: From a vague feature request, produce a ready-to-run plan that a developer can execute in a dedicated worktree.

Quick Start

Run the planning skill with a feature spec, and it will output a ready-to-run plan saved 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 generate an implementation plan from a feature spec before coding?

Create an implementation plan by processing a feature spec into bite-sized, executable tasks. The output includes explicit file modifications, test steps, and commits saved to docs/plans/YYYY-MM-DD-<feature-name>.md for traceability.

What is a TDD-aligned implementation plan and how does it structure tasks?

A TDD-aligned implementation plan structures tasks around red/green/refactor cycles and frequent commits. It breaks down multi-step software features into dedicated worktree workflows enforcing DRY and YAGNI principles.

Can I use this implementation plan approach for API and design changes?

Yes, you can use this implementation plan approach for multi-step tasks across software features, APIs, or design changes. It outputs ready-to-run tasks suitable for a dedicated worktree workflow.

What's the best way to decompose a vague feature request into executable steps?

Decompose a vague feature request by generating a step-by-step plan covering files, tests, docs, and commits. This ensures nothing important is missed and all steps are traceable before coding begins.

Does the generated plan include explicit test and commit steps for worktree workflows?

Yes, the generated plan includes explicit file, test, and commit steps ready for execution. It targets bite-sized tasks specifically designed for a dedicated worktree workflow.