subagent-driven-development

Assign implementation plan tasks to fresh subagents with two-stage review.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/rickyananda/hermes-skills --skill subagent-driven-development-rickyananda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/rickyananda/hermes-skills/tree/main/software-development/subagent-driven-development
Command: npx skills add https://github.com/rickyananda/hermes-skills --skill subagent-driven-development-rickyananda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the risk and friction of implementing large plans by breaking work into fresh subagent tasks with enforced review gates, so development stays focused, consistent, and high quality.

Core Features & Use Cases

  • Plan-to-implementation execution: Reads a prepared plan once, extracts all tasks, and drives each task through a clean subagent workflow.
  • Two-stage review: Requires spec compliance review first and code quality review second, preventing scope creep and catching defects early.
  • TDD-oriented delivery: Guides implementer subagents to write failing tests, implement the minimum change, verify success, and then re-check the full suite.
  • Integration safety: Finishes with a final end-to-end review to confirm the full implementation works together before merge.

Quick Start

Use this skill to execute the implementation plan at docs/plans/feature-plan.md by dispatching a fresh subagent for each task and requiring spec and quality review before moving on.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I delegate implementation plan tasks to subagents for software engineering?

You can delegate implementation plan tasks by extracting each task and dispatching a fresh subagent to execute it, requiring spec compliance and code quality reviews before moving on. This enforces focused, high-quality development.

What is two-stage review in subagent-driven development?

Two-stage review requires passing spec compliance review first to prevent scope creep, followed by a code quality review to catch defects early. This sequence ensures tasks meet requirements before integration.

How do I execute TDD workflows using subagents?

Subagent-driven development guides TDD execution by having subagents write failing tests, implement the minimum change, verify success, and re-check the full suite before completing the task.

Can I use subagent workflow orchestration for large, mostly independent implementation tasks?

Yes, subagent workflow orchestration applies to plan-driven, mostly independent tasks by assigning each to a fresh subagent and enforcing review gates to maintain consistency and integration safety before merge.

What is the best way to ensure integration safety when executing plans with subagents?

The best way to ensure integration safety is finishing with a final end-to-end review to confirm the full implementation works together. This prevents merging incompatible subagent task outputs.

Do I need a prepared implementation plan before starting subagent-driven development?

Yes, you need a prepared implementation plan with full task context provided once. The workflow reads the plan, extracts all tasks, and drives each through the subagent execution and review process.