subagent-driven-development

Coordinate subagent-driven development with two-stage spec and quality reviews.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill subagent-driven-development-lamseyahelias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/LamseyahElias/jarvis-cloud-v2/tree/main/hermes-agent/skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill subagent-driven-development-lamseyahelias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined orchestration framework to implement complex software tasks by dispatching fresh subagents per task and enforcing a two-stage review cycle for spec compliance and code quality.

Core Features & Use Cases

  • Per-task delegation: spawn dedicated implementer subagents for each plan item to maintain clean context and reduce cross-task contamination.
  • Two-stage review: integrate spec compliance and code quality reviewers to catch gaps early and ensure robust implementations.
  • Plan-driven execution: translate high-level requirements into executable task chunks, guaranteeing traceability and reproducibility.
  • Use Case: for a feature like "user authentication," break the work into discrete tasks (data model, endpoint, tests) and validate at each stage before merging.

Quick Start

Begin by drafting a plan, then launch implementer and reviewer subagents to execute tasks with two-stage checks.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I automate task delegation for complex software development workflows?

Automating task delegation requires a plan-driven orchestration framework that spawns dedicated implementer subagents per task. This approach maintains clean context boundaries and reduces cross-task contamination during complex software development workflows.

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

A two-stage review workflow integrates automated spec compliance checks followed by code quality reviews. This mechanism catches implementation gaps early by dispatching dedicated reviewer subagents to validate each task before final integration.

How do I break down high-level software requirements into executable task chunks?

Breaking down high-level requirements uses plan parsing to translate feature specifications into discrete, executable task chunks. This guarantees traceability and reproducibility by assigning each chunk to a fresh implementer subagent.

Can I use subagent orchestration for small software features without losing context?

Subagent orchestration suits features decomposable into independent subtasks, like user authentication. It operates within a lean context-budget, dispatching fresh subagents per task to maintain strict spec compliance and reduce context loss.

What is the best way to ensure spec compliance during automated code generation?

The best way to ensure spec compliance is orchestrating dedicated reviewer subagents after implementation. This two-stage review process validates generated code against strict specifications before final integration, guaranteeing robust implementations.

Why does cross-task contamination happen in multi-step software development?

Cross-task contamination happens when a single agent handles multiple tasks, accumulating irrelevant context. Dispatching fresh implementer subagents per task item isolates the execution context, preventing state corruption across independent subtasks.