superpowers_planning

Convert specifications into structured implementation plans with tasks, files, tests, and milestones.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JasonVene/CC_MainDev --skill superpowers-planning-jasonvene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers_planning
Source: https://github.com/JasonVene/CC_MainDev/tree/main/_archive/antigravity/.agent/skills/superpowers_planning
Command: npx skills add https://github.com/JasonVene/CC_MainDev --skill superpowers-planning-jasonvene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform a spec or requirements for a multi-step task into a complete implementation plan, including the steps, files, tests, and milestones needed to convert ideas into working code.

Core Features & Use Cases

  • Generates bite-sized, test-driven task steps with explicit file paths and test examples.
  • Provides a structured plan document (task.md and implementation_plan.md) for traceability and iteration.
  • Supports collaboration by clearly outlining responsibilities and checkpoints for engineers, QA, and docs.

Quick Start

Provide a spec and I will generate a complete implementation plan saved as task.md and implementation_plan.md.

Frequently Asked Questions about superpowers_planning

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

FAQPage Schema
How do I convert software specifications into an actionable implementation plan?

You can convert specs into an implementation plan by generating a structured document with explicit bite-sized task steps, file paths, test examples, and milestones for traceability.

What is the best way to plan multi-step software engineering tasks?

The best way to plan multi-step software engineering tasks is to generate a structured plan document outlining bite-sized, test-driven steps and clear responsibilities for engineers, QA, and docs.

How do I generate test-driven task steps from a project spec?

You can generate test-driven task steps from a spec by using a planning workflow that outputs bite-sized tasks with explicit file paths and test examples saved as task.md and implementation_plan.md.

Do I need to provide a full requirements document to create a task plan?

You do not need a full requirements document; providing a spec or basic requirements for your multi-step task is sufficient to generate a complete implementation plan with necessary steps, files, and tests.

Can I include scripts and reference assets in my implementation plan?

Yes, you can include optional resources in scripts, references, and assets directories as needed to support your generated implementation plan and provide additional context for the engineering team.