subagent

Orchestrate small issues by spawning Phase A/B/C subagents to implement, review, and merge changes.

3|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill subagent-auerbachb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/subagent
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill subagent-auerbachb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run small issues as subagents directly from a PM thread. Validate complexity, spawns Phase A/B/C agents, monitors progress, and reports merge readiness. Use when small issues should be executed inline instead of in separate coding threads.

Core Features & Use Cases

  • Validate issue complexity and orchestrate multi-phase workflows across Phase A, B, and C.
  • Spawn Phase A subagents to implement changes, then Phase B for review and Phase C for merge prep, all within a PM context.
  • Monitor progress, handle handoffs, and report merge readiness back to the PM thread.
  • Support multi-issue inputs and automatic fallbacks if explicit plans are unavailable.

Quick Start

Invoke the subagent in a PM thread with one or more issue numbers to start Phase A and automatically orchestrate Phase B and Phase C as needed.

Frequently Asked Questions about subagent

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

FAQPage Schema
How do I automate small issue orchestration directly from a project management thread?

Automating small issue orchestration from a PM thread involves spawning multi-phase subagents to implement, review, and merge changes. This workflow validates issue complexity and reports merge readiness without requiring separate coding threads.

What is the multi-phase subagent protocol for code review and merge automation?

The multi-phase subagent protocol uses Phase A to implement changes, Phase B to review code, and Phase C to prepare merges. It operates from a PM thread to monitor progress and manage handoffs across agents.

Can I run multiple small issues through automated subagent workflows at the same time?

Yes, you can run multiple small issues simultaneously by invoking the subagent with multiple issue numbers. It supports multi-issue inputs and provides automatic fallbacks if explicit plans are unavailable.

When should I use inline subagent orchestration instead of separate coding threads?

Inline subagent orchestration is used when small issues should be executed directly within a PM context. It validates that issue complexity is low enough to avoid spinning up separate coding threads for implementation.

Does automated issue orchestration work without an explicit implementation plan?

Automated issue orchestration includes automatic fallbacks when explicit plans are unavailable. The rule-based prompt system manages work across agents to ensure changes are still implemented, reviewed, and prepared for merging.

What are the limitations of using subagent workflows for issue resolution?

Subagent workflows are limited by issue complexity validation, restricting use to small issues suitable for inline PM thread execution. Larger, complex issues require separate coding threads rather than this automated multi-phase approach.