skills.rest
fts-pro
fts-proCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generates detailed multi-step implementation plans with TDD tasks from feature specifications.

Updated May 18, 2026
Search Tags:#planning#tdd#markdown#code generation#implementation plan#task decomposition#spec
One-click install
npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill writing-plans-fts-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/fts-pro/FTS-MMIS-AFRIKA/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill writing-plans-fts-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature spec into code without a plan leads to missed requirements, vague tasks, and inconsistent execution. This Skill converts a specification into a complete, bite-sized implementation plan that an engineer with zero codebase context can follow task by task. ## Core Features & Use Cases - Bite-Sized TDD Tasks: Breaks work into 2-5 minute steps following the write-failing-test, implement, verify, commit cycle. - No-Placeholder Enforcement: Requires exact file paths, complete code blocks, and exact commands with expected output in every step. - Self-Review and Handoff: Includes a spec-coverage and consistency self-review checklist, plus an execution handoff offering subagent-driven or inline execution. - Use Case: Given a spec for a new API endpoint, produce a dated plan document in docs/superpowers/plans/ with checkbox tasks covering tests, implementation, and commits for each component. ## Quick Start Use the writing-plans skill to turn my feature spec into a step-by-step implementation plan with TDD tasks.

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?▼

Provide the spec and invoke the writing-plans skill before touching code. It maps the file structure, decomposes work into bite-sized TDD tasks with exact paths and code, and saves the plan to docs/superpowers/plans/ with a dated filename.

What makes a good task breakdown for implementation plans?▼

Each step should be one action taking 2-5 minutes: write the failing test, run it to confirm failure, implement minimal code, verify it passes, then commit. Every step needs exact file paths, complete code blocks, and commands with expected output.

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 execution verifiable.

What are common mistakes in AI-generated implementation plans?▼

Common failures include placeholders like TODO or 'add error handling', missing code in steps, inconsistent type or method names across tasks, and requirements from the spec with no corresponding task. The self-review checklist catches these before execution.

How are completed plans executed after writing?▼

After saving, the plan offers two execution paths: subagent-driven development, which dispatches a fresh subagent per task with review between tasks, or inline execution with batch processing and checkpoints.

Related Skills

Explore More Software Engineering Skills→
stevengonsalvezstevengonsalvez

brainstorm

Turn vague ideas into a structured spec.md with iterative questioning.

Community
Intermediate
DJ2695DJ2695

subagent-driven-development

Dispatch a fresh subagent for each task with spec compliance and code quality reviews.

Community
Advanced
ryanportfolioryanportfolio

writing-plans

Generates structured implementation plans from specs before writing code.

Community
Intermediate
busboom-software-studiobusboom-software-studio
1

oop

Apply small targeted changes directly on master with test suite runs.

Official
Intermediate