Index of every page on this site: llms.txt
All skills
obra avatar

/subagent-driven-development

@2ce8aa1 official
by Jesse Vincentobra/superpowers312k stars
27,731
Run it yourself

Use when executing implementation plans with independent tasks in the current session

Use this Skill: https://skilld.dev/gh/obra/superpowers/subagent-driven-development

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencescannot-verify.md

≈129 tokens on demand. Your agent reads this file only when SKILL.md points to it.

"Cannot Verify From Diff" Items

Part of superpowers:subagent-driven-development.

The task reviewer may report "⚠️ Cannot verify from diff" items — requirements that live in unchanged code or span tasks. These do not block the rest of the review, but you must resolve each one yourself before marking the task complete: you hold the plan and cross-task context the reviewer lacks. If you confirm an item is a real gap, treat it as a failed spec review — it enters the fix loop with the other findings.

Source: SKILL.md on GitHub

Skill behaviors

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

Third-party checks

No alerts12d5 checks · Risk SAFE
  • Gen Agent Trust Hub12d

    This skill provides a structured workflow for executing implementation plans using subagents and local scripts for task management and review. It is categorized as low risk due to the potential for indirect prompt injection, as the agent processes external plans and subagent reports, though the included multi-agent review process and explicit security stopping conditions provide mitigation.

  • Socket12d

    No alerts

  • Snyk12d

    Risk: LOW · No issues

  • Runlayer7mo

    4 files scanned · No issues

  • ZeroLeaks6mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 2ce8aa1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Activeupdated 2 weeks ago

Topics

  • subagents
  • implementation
  • planning
  • code-review
  • task-dispatch
  • spec-compliance
  • quality-review
  • workflow

README badge

README badge for obra/superpowers/subagent-driven-development

What it does

Dispatch independent implementation tasks to fresh subagents with two-stage review (spec compliance, then code quality) after each. Targets execution of detailed plans where tasks have minimal interdependencies and you need to stay in the current session without human checkpoints between tasks.

Generated from the current SKILL.md.

Frequently asked

When should I use subagent-driven development instead of manual execution?
Use this skill when you have an implementation plan with mostly independent tasks and want to stay in the same session. It's not suited for tightly coupled tasks that require back-and-forth coordination — in that case, execute tasks manually or use the executing-plans skill.
Do I need to wait between tasks, or does the skill execute continuously?
The skill executes all tasks continuously without pausing for check-ins. You only stop if a task is blocked, genuinely ambiguous, or all tasks are complete. Progress summaries and "should I continue?" prompts waste time — the human asked you to execute the plan.
What models should I use for different task types?
Use a fast, cheap model for mechanical implementation (isolated functions, clear specs). Use a standard model for integration tasks (multi-file coordination). Use the most capable model for architecture and design tasks. Match model power to task complexity to save cost and speed.
What do I do if a subagent returns BLOCKED status?
Assess the blocker: if it's a context problem, provide more information and re-dispatch with the same model. If it needs more reasoning, re-dispatch with a more capable model. If the task is too large, break it smaller. If the plan is wrong, escalate to the human. Never ignore the blocker or force the same model to retry unchanged.
What's the correct order for reviews?
Always run spec compliance review first, then code quality review. Starting code quality review before spec compliance is verified is wrong. If either review finds issues, the implementer subagent fixes them and the reviewer reviews again until approved.

Generated from the current SKILL.md. These answers refresh after source changes.