skills.rest
susantosanto
susantosantoCOMMUNITY
Explore all skills by this author →
GitHub

superpowers-writing-plans

Translate approved specs into structured implementation plans with tasks and architecture.

Updated Apr 4, 2026
Search Tags:#architecture#documentation#implementation#spec#plan#task-breakdown
One-click install
npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-writing-plans-susantosanto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: superpowers-writing-plans
Source: https://github.com/susantosanto/config-opencode/tree/main/skills/superpowers-writing-plans
Command: npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-writing-plans-susantosanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts approved design specs into a structured, actionable implementation plan, reducing ambiguity and guiding execution.

Core Features & Use Cases

  • Structured plan: Goal, Architecture, Tech Stack, and a comprehensive list of Tasks with File Paths, Steps, and Expected Outcomes.
  • Task-focused execution: Each Task includes Create/Modify/Test paths, step-by-step instructions (Test first, then Code, then Verify), and optional code blocks when needed.
  • Reproducible documentation: Save the final plan as a Markdown document under a documented path for traceability and handoff.

Quick Start

Create an implementation plan from an approved spec and save it to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md

Frequently Asked Questions about superpowers-writing-plans

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

FAQPage Schema
How do I turn an approved design spec into an executable implementation plan?▼

To turn a spec into an implementation plan, you translate approved requirements into a structured document containing Goal, Architecture, Tech Stack, and comprehensive Tasks with file paths and step-by-step execution instructions.

What is the best way to break down software development tasks from requirements?▼

Task breakdown from requirements involves generating a list of executable actions specifying Create, Modify, and Test file paths, along with step-by-step instructions to test first, then code, and finally verify the expected outcome.

How do I document architecture decisions and tech stack choices for a new feature?▼

Documenting architecture and tech stack choices requires structuring them into predefined sections of an implementation plan, ensuring reproducible documentation and traceable handoff from design to development workflows.

Can I save implementation plans as Markdown files for future reference and handoff?▼

Yes, you can save implementation plans as Markdown documents under a specific path, such as docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md, ensuring reproducible documentation and traceable project handoff.

Do I need an approved spec before generating an implementation plan?▼

Yes, an approved spec is required beforehand because the implementation plan translates those specific design requirements into structured architecture decisions and actionable task lists for development execution.

Related Skills

Explore More Product & Management Skills→
micaelmaltamicaelmalta
1

architect

Draft technical specifications covering architecture, APIs, data models, and migrations.

Community
Advanced
Bbeierle12Bbeierle12
8

writing-plans

Generate task-by-task implementation plans with tests and rollback guidance.

Community
Basic
slashwhyslashwhy
5

architectural-documentation

Generate templates for implementation plans, ADRs, API specifications, and migration guides.

Official
Basic
telum-aitelum-ai
2

epic-breakdown

Generate user stories, dependencies, and parallelization opportunities from epic specifications.

Official
Advanced