writing-plans

Decompose specs into TDD-friendly implementation plans with exact file paths and commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

writing-plans turns messy specs or requirements into a build-ready implementation plan so an engineer can execute task-by-task without guessing.

Core Features & Use Cases

  • Multi-step TDD-friendly decomposition: Breaks work into bite-sized tasks (typically 2–5 minutes each) with explicit test, implementation, verification, and commit steps.
  • File-accurate change mapping: Specifies exact file paths to create/modify and keeps responsibilities well-bounded to reduce context switching.
  • No-placeholder, buildable outputs: Enforces complete content in each step, including actual code blocks, exact commands, and expected outputs.
  • Spec coverage self-review: Requires checking the final plan against the spec to identify gaps and placeholder risks before handoff.

Quick Start

Use the writing-plans skill when you have a spec or requirements for a multi-step task and need an implementation plan before touching code.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn software requirements into a build-ready implementation plan?

Decompose multi-step feature work into executable, test-first tasks to produce a build-ready implementation plan. This plan maps exact file paths and specifies testing, verification, and commit-ready iteration steps to ensure an engineer can execute without missing context.

What is the best way to break down a multi-step feature spec for TDD?

Break down a multi-step feature spec for TDD by generating 2–5 minute bite-sized tasks that each include explicit testing, implementation, and verification steps. This decomposition ensures task responsibilities remain well-bounded and reduces context switching across the codebase.

How do I map out exact file changes before starting implementation?

Map out exact file changes by specifying precise file paths to create or modify within the implementation plan. This file-accurate change mapping keeps responsibilities well-bounded and reduces context switching during multi-step feature development.

Can I generate a development plan that includes commit-ready iteration steps?

Yes, you can generate a development plan that includes commit-ready iteration steps by decomposing work into tasks with explicit test, implementation, verification, and commit phases. Each task is designed to be fully buildable and executable without guessing.

How do I ensure my implementation plan has no missing context or placeholders?

Ensure an implementation plan has no missing context or placeholders by enforcing strict no-placeholder rules that require complete content in each step, including actual code blocks and exact commands. A spec coverage self-review checks the final plan against the spec to identify gaps.