superpowers-workflow

Coordinate a structured, test-driven software development workflow across planning, implementation, testing, and review phases.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Lutra23/content-workflow --skill superpowers-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-workflow
Source: https://github.com/Lutra23/content-workflow/tree/main/skills/superpowers-workflow
Command: npx skills add https://github.com/Lutra23/content-workflow --skill superpowers-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate a disciplined, structured software development workflow from ideation through delivery, emphasizing tests, reviews, and incremental tasks to improve predictability and quality.

Core Features & Use Cases

  • Brainstorming to plan: Define scope, success criteria, and constraints before breaking work into tasks.
  • Task-based implementation: Break work into small, testable tasks with file- and verification-based requirements.
  • Quality gates: Integrate TDD, code reviews, and finishing criteria to ensure code quality and traceability.

Quick Start

Coordinate a structured development workflow from idea to shipped feature by following brainstorming, planning, implementation, testing, and finishing phases.

Frequently Asked Questions about superpowers-workflow

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

FAQPage Schema
How do I structure a test-driven development workflow from brainstorming to delivery?

A structured test-driven development workflow coordinates ideation through delivery across brainstorming, planning, implementation, testing, review, and finishing phases. It enforces task-level planning with file-level requirements and documented finishing criteria to improve predictability and quality.

What is incremental delivery in agile software development?

Incremental delivery in agile development breaks project scope into small, testable tasks with clear verification requirements. It applies phase-gated processes across implementation and review to ensure code quality and traceability before finishing.

How do I integrate code reviews into an agile workflow?

Integrating code reviews into an agile workflow applies quality gates between implementation and finishing phases. This structured approach ensures tasks meet file-level verification requirements and documented finishing criteria before delivery.

Can I use this workflow for planning tasks before writing any code?

Yes, the workflow explicitly covers a brainstorming-to-plan phase to define scope, success criteria, and constraints before implementation. It breaks work into small, testable tasks with file-based and verification-based requirements.

Does test-driven development work with incremental task-based implementation?

Test-driven development pairs naturally with incremental task-based implementation by enforcing quality gates on small, testable units. Each task carries explicit verification requirements ensuring traceability before passing the code review and finishing phases.

What is the best way to define finishing criteria for an agile feature?

The best way to define finishing criteria is establishing documented requirements during the planning phase before implementation begins. This structured workflow applies phase-gated quality checks including TDD and code reviews to verify criteria are met.