superpowers-subagent-driven-development

Orchestrate isolated implementer and reviewer loops for large task lists.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill superpowers-subagent-driven-development-miss-pinkelf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-subagent-driven-development
Source: https://github.com/Miss-PinkElf/Multi-Agent/tree/main/.claude/skills/spark-workflow/skills/superpowers-subagent-driven-development
Command: npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill superpowers-subagent-driven-development-miss-pinkelf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This approach solves the challenge of managing large task lists by enforcing isolated implementer and reviewer loops to maintain quality and preserve context.

Core Features & Use Cases

  • Pattern-driven task cycles: assign, implement, review, and gate tasks before closure.
  • Best fits for large codebases and complex systems requiring separation between development and verification.
  • Guardrails ensure coordination and prevent premature approvals.

Quick Start

Assign each task to a dedicated implementer with exact task text, artifact context, and acceptance criteria, then run the implementer's work through spec-compliance and code-quality reviews.

Frequently Asked Questions about superpowers-subagent-driven-development

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

FAQPage Schema
How do I manage large task lists while maintaining code quality?

Manage large task lists by orchestrating isolated implementer and reviewer loops, enforcing sequential spec-compliance and code-quality reviews before task closure to maintain quality and preserve context.

What is subagent-driven development for complex systems?

Subagent-driven development is a pattern that separates development from verification by assigning tasks to dedicated implementers and running their work through independent reviewer cycles.

How do I enforce spec compliance before closing a development task?

Enforce spec compliance by requiring explicit task text, artifact context, and acceptance criteria, then gating task closure until a dedicated reviewer successfully completes a spec-compliance review.

Can I use implementer and reviewer loops within a SPARK-workflow context?

Yes, this task management approach applies specifically to large task lists within SPARK-workflow contexts where individual tasks benefit from separate implementer and reviewer cycles.

Does subagent task breakdown work for small codebases?

Subagent task breakdown best fits large codebases and complex systems requiring strict separation between development and verification, rather than smaller or simpler projects.