superpower-writing-plans

Transform vague specifications into explicit task-scoped implementation plans.

Updated Aug 23, 2026

Search Tags:#spec-to-plan #task-decomposition #plan-generation #feature-planning #docs-plans #tdd-planning

Ready to run

npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-writing-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpower-writing-plans
Source: https://github.com/fernandoxavier02/Codex-superpower/tree/main/skills/writing-plans
Command: npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-writing-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers convert vague requirements into explicit, task-scoped implementation plans that define which files to touch, what tests to write, how to document, and how to commit progress.

Core Features & Use Cases

Plan decomposition of specs into concrete tasks and milestones.
Task traceability from plans to files, tests, and commits.
Documentation-oriented guidance for multi-step development workflows, including TDD and incremental delivery.

Quick Start

Provide a complete implementation plan for a new feature by breaking it into tasks, files, tests, and commits.

Frequently Asked Questions about superpower-writing-plans

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

FAQPage Schema

How do I decompose software specifications into actionable implementation tasks?▼

To break down feature specifications into actionable tasks, this Skill transforms vague requirements into explicit, task-scoped milestones that define exact file lists, test cases, and commit messages for execution.

What is the best way to plan TDD-style iterations for a multi-step feature?▼

Planning TDD-style iterations involves generating structured development workflows that enforce clear task boundaries and concrete outputs, ensuring each step traces directly to specific test cases, incremental code delivery, and documentation updates.

How do I generate execution-ready plans that include file lists and commit messages?▼

Generating execution-ready plans involves converting high-level specs into explicit task boundaries that output concrete deliverables, including targeted file lists, required test cases, and structured commit messages to guide incremental implementation.

Can I use task decomposition planning for both code implementation and documentation workflows?▼

Yes, task decomposition planning applies to multi-step development goals across code, tests, and documentation, ensuring that every planned milestone includes concrete outputs and traceable boundaries for both implementation and docs.

What are the limitations of generating implementation plans from vague requirements?▼

A key limitation of generating implementation plans from vague requirements is that the resulting task boundaries and concrete outputs rely heavily on the initial spec's clarity, requiring explicit milestone definitions to avoid ambiguous execution paths.