skills.rest
svssdeva
svssdevaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Convert ambiguous requirements into testable implementation plans with exact file paths.

1|1|Updated Apr 20, 2026
Search Tags:#implementation planning#task breakdown#test-driven development#engineering workflow#git commits#developer documentation#spec decomposition
One-click install
npx skills add https://github.com/svssdeva/agentic-skills --skill writing-plans-svssdeva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/svssdeva/agentic-skills/tree/main/engineering/writing-plans
Command: npx skills add https://github.com/svssdeva/agentic-skills --skill writing-plans-svssdeva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of unclear, hard-to-execute specifications by turning requirements into a concrete, testable execution plan before any code is touched.

Core Features & Use Cases

  • Spec-to-plan decomposition: Breaks multi-subsystem specs into independent plans and maps which files to create or modify.
  • Bite-sized TDD tasks: Converts each step into 2–5 minute actions (write failing test, verify failure, implement minimal code, verify pass, commit).
  • Code-and-commands included: Enforces no placeholders, includes exact file paths, complete code blocks for changed code, and exact test/commit commands.
  • Plan persistence: Saves plans to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md (or a user-preferred override location) and provides an execution handoff with subagent or inline options.

Quick Start

Use the writing-plans skill to produce an implementation plan for a feature spec, saving it into docs/superpowers/plans with a dated filename.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn ambiguous feature specs into step-by-step implementation plans?▼

Spec decomposition breaks multi-subsystem feature specs into independent, actionable implementation plans. It maps exact file paths to create or modify, converting each requirement into 2-5 minute test-driven tasks with complete code blocks and commit commands.

What's the best way to break engineering specs into test-driven development tasks?▼

Test-driven task breakdown converts each spec step into 2-5 minute actions: write a failing test, verify failure, implement minimal code, verify pass, and commit. This creates bite-sized, repeatable execution workflows with complete code and exact commands.

How do I generate an implementation plan with exact file paths and complete code blocks?▼

Implementation plan generation enforces no placeholders by including exact file paths for files to create or modify, complete code blocks for changed code, and exact test and git commit commands. This ensures every task step is fully executable without guessing.

Does implementation planning work for multi-step features requiring file-level decomposition?▼

Implementation planning suits multi-step feature work requiring file-level decomposition. It handles multi-subsystem specs by breaking them into independent plans, making complex engineering workflows repeatable and testable before development begins.

Where are generated implementation plans saved for developer documentation?▼

Generated implementation plans save to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. You can specify a user-preferred override location to integrate with existing developer documentation workflows and execution handoffs.

Can I hand off a test-driven implementation plan to a subagent for execution?▼

Implementation plans provide execution handoff options for subagent or inline execution. The saved plan contains structured, testable tasks with exact paths and commands, allowing automated agents to execute the development workflow step by step.

Related Skills

Explore More Software Engineering Skills→
devMoezdevMoez
1

writing-plans

Generate repository-aware implementation plans with test-driven steps.

Community
Intermediate
PlazaCCPlazaCC
2

subagent-driven-development

Execute implementation plan tasks with fresh subagents and two-stage reviews.

Official
Advanced
wise-clawwise-claw
10

trellis-finish-work

Verify task completion, archive Trellis tasks, and record session progress.

Official
Intermediate
Kafil99Kafil99

constitution_guard

Validate project adherence to SDD principles and detect scope creep.

Community
Advanced