writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from feature specifications.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/D1ssolve/craft-agents --skill writing-plans-d1ssolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/writing-plans
Command: npx skills add https://github.com/D1ssolve/craft-agents --skill writing-plans-d1ssolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often start coding from a spec without a clear roadmap, leading to missed requirements, inconsistent structure, and untested code. This Skill turns a spec or requirements document into a complete, step-by-step implementation plan that any developer can execute without prior codebase context. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following a strict TDD cycle (failing test, minimal implementation, verification, commit). - Zero-Placeholder Enforcement: Requires exact file paths, complete code blocks, exact commands, and expected outputs in every step, banning vague instructions like "add error handling". - Self-Review Checklist: Validates the finished plan against the spec for coverage gaps, placeholder patterns, and type/name consistency across tasks. - Use Case: Given a spec for a new API endpoint, produce a plan saved to docs/superpowers/plans/ with checkbox tasks covering file structure, tests, implementation code, and commit commands. ## Quick Start Ask the agent to use the writing-plans skill to create an implementation plan from your feature specification document.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan from a feature spec?

Map out the file structure first, then decompose work into tasks with exact file paths, complete code blocks, and test commands. Each step should take 2-5 minutes and follow a failing-test, implement, verify, commit cycle.

What is the best task granularity for an implementation plan?

Each step should be one action taking 2-5 minutes, such as writing a failing test, running it to confirm failure, implementing minimal code, verifying it passes, and committing. Larger steps hide errors and make progress hard to track.

When should a spec be split into multiple implementation plans?

Split when the spec covers multiple independent subsystems. Each plan should produce working, testable software on its own, so one plan per subsystem keeps scope manageable and deliverables verifiable.

Why do implementation plans fail during execution?

Plans fail when they contain placeholders like TBD or vague steps such as "add error handling", reference undefined types or functions, or use inconsistent names across tasks. A self-review pass against the spec catches these issues.

Where should implementation plan documents be saved?

By default, plans are saved to docs/superpowers/plans/ with a filename pattern of YYYY-MM-DD-feature-name.md. User preferences for plan location override this default.