skills.rest
erwinv2k-TKG
erwinv2k-TKGCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

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

Updated Mar 26, 2026
Search Tags:#tdd#software development#implementation plan#task decomposition#spec#subagent#code planning
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill writing-plans-erwinv2k-tkg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/superpowers/skills/writing-plans
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill writing-plans-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: tasks are often too vague, file paths are missing, and engineers without codebase context get stuck. This Skill produces a complete, step-by-step plan that an engineer (or agent) with zero context can execute. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following TDD: write failing test, verify failure, implement, verify pass, commit. - Exact File Mapping: Every task lists exact files to create or modify, complete code snippets, and exact commands with expected output. - 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, use this Skill to produce a dated plan document in docs/superpowers/plans/ that a fresh subagent can implement task-by-task with checkbox tracking. ## Quick Start Ask the agent to use the writing-plans skill to turn your feature spec into a step-by-step implementation plan saved under docs/superpowers/plans/.

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 or requirements, then map out which files will be created or modified before defining tasks. Break the work into bite-sized TDD steps: write a failing test, verify it fails, implement minimal code, verify it passes, and commit.

How detailed should tasks in an implementation plan be?▼

Each step should be a single 2-5 minute action with exact file paths, complete code snippets, and exact commands with expected output. Avoid vague instructions like 'add validation' since the implementer may have zero codebase context.

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 reviewable.

How do I verify an implementation plan is complete before coding?▼

Dispatch a plan-document-reviewer subagent with the plan path and spec path. It checks completeness, spec alignment, task decomposition, and buildability, returning Approved or Issues Found; fix issues and re-review until approved.

What are the options for executing a finished implementation plan?▼

Two options exist: subagent-driven development, which dispatches a fresh subagent per task with review between tasks, or inline execution, which runs tasks in the current session in batches with checkpoints.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

brainstorming

Shape vague product ideas into clear design directions before implementation.

Community
Advanced
christopherarterchristopherarter
90

superpowers-writing-plans

Translate software specifications into structured development plans with tests and commits.

Community
Advanced
Fancu1Fancu1

subagent-driven-development

Execute implementation plans by dispatching subagents for each task with two-stage review.

Community
Advanced
wojonswojons
4

testing-level-poc

Define minimal manual and unit testing strategies for Proof of Concept projects.

Community
Basic