subagent-driven-development

Dispatch specialized subagents for development tasks with two-stage reviews.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill subagent-driven-development-haru-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse/tree/main/.agent/skills/engineering/subagent-driven-development
Command: npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill subagent-driven-development-haru-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distributes development tasks to dedicated subagents, enabling parallel work with a built-in two-stage review process to improve quality and speed.

Core Features & Use Cases

  • Subagent orchestration: assigns tasks to specialized subagents per need
  • Two-stage reviews: ensures quality via reviewer roles before integration
  • Plan-then-execute workflow: from task planning to completion with traceability
  • Use Case: For large features requiring multiple subagents (frontend, backend, tests) to operate in a single session with handoffs

Quick Start

Provide a task description to initiate, and the system will dispatch subagents and begin the two-stage review workflow.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I use subagents to parallelize development tasks?

Subagent orchestration dispatches specialized subagents to execute development tasks concurrently, enabling parallel work across frontend, backend, and tests with minimal handoffs. It tracks context and enforces review cycles to maintain quality during fast iterations.

What is a two-stage review workflow in software development?

A two-stage review workflow enforces quality via dedicated reviewer roles before integrating completed tasks. It ensures that subagent-generated code meets standards by routing tasks through planning, execution, review, and integration phases with full traceability.

Can I use subagent orchestration for large features requiring multiple handoffs?

Subagent orchestration is designed for large features requiring multiple subagents to operate in a single session. It manages handoffs between frontend, backend, and testing subagents while enforcing two-stage reviews to maintain quality standards.

Does subagent-driven development work without external dependencies?

Subagent-driven development operates without external dependencies. It uses internal orchestration to route tasks to specialized subagents, track context, and enforce review cycles, satisfying planning, execution, review, and integration requirements natively.

When should I not use a subagent orchestration approach for development?

Subagent orchestration may be excessive for simple, single-agent tasks that do not require two-stage reviews or parallel execution. It is designed for complex engineering workflows where multiple specialized subagents need to operate with minimal handoffs and enforced quality assurance.