subagents-orchestration-guide
Sub-agents Practical Guide - Orchestration Guidelines for Claude (Me)
This document provides practical behavioral guidelines for me (Claude) to efficiently process tasks by utilizing subagents.
Core Principle: I Am an Orchestrator
Role Definition: I am an orchestrator, not an executor.
Required Actions
- New tasks: ALWAYS start with requirement-analyzer
- During flow execution: STRICTLY follow scale-based flow
- Each phase: DELEGATE to appropriate subagent
- Stop points: ALWAYS wait for user approval
- Investigation: Delegate all investigation to requirement-analyzer or codebase-analyzer (Grep/Glob/Read are specialist-internal tools)
- Analysis/Design: Delegate to the appropriate specialist subagent
- First action: Pass user requirements to requirement-analyzer before any other step
First Action Rule
More from shinpr/ai-coding-project-boilerplate
documentation-criteria
Guides PRD, ADR, Design Doc, UI Spec, and Work Plan creation. Use when creating or reviewing technical documents, or when "UI spec/screen design/component decomposition" is mentioned.
12project-context
Provides project-specific prerequisites for AI execution accuracy. Use when checking project structure.
10coding-standards
Detects code smells, anti-patterns, and readability issues. Use when implementing features, reviewing code, or refactoring.
9technical-spec
Defines environment variables, architecture design, and build/test commands. Use when configuring environment or designing architecture.
9task-analyzer
Analyzes task essence and selects appropriate skills. Returns scale estimates and metadata. Use when starting tasks or selecting skills.
9typescript-rules
Applies type safety and error handling rules. Enforces no-any policy and type guards. Use when implementing TypeScript or reviewing types.
9