writing-plans

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

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill writing-plans-grupo-6-ads-b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Grupo-6-ADS-B/FittNutri/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill writing-plans-grupo-6-ads-b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often start coding multi-step features without a clear roadmap, leading to missed requirements, inconsistent structure, and rework. This Skill turns a spec or requirements document into a complete, step-by-step implementation plan that any developer can follow without prior codebase context. ## Core Features & Use Cases - Structured Plan Generation: Produces plans with exact file paths, complete code snippets, test commands with expected output, and commit steps, organized as bite-sized checkbox tasks. - TDD Task Decomposition: Breaks work into 2-5 minute steps following the write-failing-test, implement, verify, commit cycle, enforcing DRY, YAGNI, and frequent commits. - Plan Review Loop: Dispatches a plan-document-reviewer subagent to verify completeness and spec alignment before execution, then offers subagent-driven or inline execution handoff. - Use Case: After brainstorming a new feature spec, invoke this Skill to produce a dated plan document in docs/superpowers/plans/ that a fresh engineer or subagent can execute task-by-task. ## Quick Start Ask the AI 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 before coding a feature?

Start from a spec or requirements document, map out which files will be created or modified, then decompose the work into bite-sized tasks. Each task should include exact file paths, complete code, test commands with expected output, and a commit step.

What is the best way to break a coding task into TDD steps?

Split each task into 2-5 minute steps: write the failing test, run it to confirm failure, write the minimal implementation, run the test to confirm it passes, then commit. This keeps changes small, verifiable, and easy to review.

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 focused and execution manageable.

How do I review an implementation plan before executing it?

Dispatch a plan-document-reviewer subagent with the plan file path and spec file path. It checks completeness, spec alignment, task decomposition, and buildability, returning Approved or Issues Found with specific feedback.

What are the limitations of plan-driven development?

Plans assume the spec is accurate and complete, so vague requirements produce vague plans. If the review loop exceeds three iterations without approval, the guidance is to surface the disagreement to a human rather than continue cycling.