subagent-driven-development

Dispatch fresh subagents to execute independent tasks with two-stage spec and code quality reviews.

1.5k|69|Updated Mar 13, 2025
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill subagent-driven-development-uniclipboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.claude/skills/subagent-driven-development
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill subagent-driven-development-uniclipboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate plan execution by dispatching fresh subagents to tackle independent tasks within a single session, eliminating context-switch overhead and manual handoffs.

Core Features & Use Cases

  • Fresh per-task subagents ensure isolated context and clean execution.
  • Two-stage review workflow (spec compliance, then code quality) improves iteration quality.
  • Built-in templates for implementer, spec-reviewer, and code-quality-reviewer streamline governance across tasks.

Quick Start

Start by dispatching a new implementer subagent for each task and run two-stage reviews (spec then quality) after each task.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I orchestrate subagents to execute development tasks in parallel?

You orchestrate subagents by dispatching fresh, isolated subagents for each independent task within a single session. This eliminates context-switching overhead and manual handoffs, enabling rapid iteration across multi-task development scenarios.

What is a two-stage code review workflow and how does it improve development quality?

A two-stage review workflow enforces quality by running a spec compliance review first, followed by a code quality review. Using dedicated templates for each stage ensures structured quality gates across all dispatched tasks.

How do I prevent context switching overhead when running multiple development tasks?

Prevent context switching by dispatching fresh per-task subagents that maintain isolated context and clean execution. This approach eliminates manual handoffs and ensures each task operates independently within the session.

Does subagent-driven development require external dependencies or templates?

Subagent-driven development requires no external dependencies. It provides built-in templates for the implementer, spec-reviewer, and code-quality-reviewer roles to streamline governance and interaction across tasks.

What's the best way to structure subagent prompts for spec compliance and code quality reviews?

The best way is using built-in templates that define specific prompts for the implementer, spec-reviewer, and code-quality-reviewer. These templates govern their interaction to enforce structured quality gates.

When should I use subagent orchestration instead of manual task execution?

Use subagent orchestration when tackling multi-task development scenarios that require rapid iteration. It eliminates manual handoffs by dispatching fresh subagents with isolated context for each independent task.