Favicon of subagent-driven-development

subagent-driven-development Skill

AI Agent SkillJavaScriptOpen source

Use when executing implementation plans with independent tasks in the current session Published by openai in plugins.

Decision snapshot

Is this a fit?

Best for

Developers using plugins, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

12 days ago

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is subagent-driven-development Skill?

Use when executing implementation plans with independent tasks in the current session Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
93/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Developers using plugins

Declared skill metadata

  • Source file: plugins/superpowers/skills/subagent-driven-development/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use subagent-driven-development Skill

  • Use it for developers using plugins.

Built with

JavaScriptCopy skill directory

Editorial notes

Source

  • Creator: openai
  • Repository: openai/plugins
  • Skill file: plugins/superpowers/skills/subagent-driven-development/SKILL.md

What it does

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

Skill instructions

Subagent-Driven Development Execute plan by dispatching a fresh implementer subagent per task, a task review (spec compliance + code quality) after each, and a broad whole-branch review at the end. Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work. Core principle: Fresh subagent per task + task review (spec + quality) + broad final review = high quality, fast iteration Narration: between tool calls, narrate at most one short line — the ledger and the tool results carry the record. Continuous execution: Do not pause to check in with your human partner between tasks. Execute all tasks from the plan without stopping. The only reasons to stop are the four named below, or all tasks complete. "Shoul

Verified compatibility and discovery

Frequently asked questions

What is subagent-driven-development?

subagent-driven-development is a open-source AI agent skill with Copy skill directory. Use when executing implementation plans with independent tasks in the current session

Who is subagent-driven-development best for?

subagent-driven-development is best for reusing agent instructions, scripts, and references.

How do I install subagent-driven-development?

Install or run subagent-driven-development using Copy skill directory. Check subagent-driven-development for the latest setup command.

Is subagent-driven-development actively maintained?

subagent-driven-development may need a closer maintenance check before production use.

Share:

Stars
5,411
Forks
776
Last commit
12 days ago
Last verified
Sep 6, 2026
Metadata fetched
Sep 6, 2026
Repository age
6 months
License
Unknown

Project health auto-fetched from the source repository.

Maintain this resource?

Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.

Alternatives to subagent-driven-development