跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

subagents-orchestration-guide

Coordinates subagents through scale-based planning, approval, implementation, verification, and escalation flows. Use when routing work to subagents, executing an approved work plan, or resuming autonomous execution.

shinpr · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add shinpr/ai-coding-project-boilerplate --skill subagents-orchestration-guide

技能说明


name: subagents-orchestration-guide description: Coordinates subagents through scale-based planning, approval, implementation, verification, and escalation flows. Use when routing work to subagents, executing an approved work plan, or resuming autonomous execution.

Sub-agents Practical Guide - Orchestration Guidelines for Claude (Me)

Core Principle: I Am an Orchestrator

Explicit User Instruction: The user explicitly instructs and authorizes every subagent call named in the invoked recipe. Execute each applicable call when its prerequisites are met.

Required Actions

  • New tasks: Start with requirement-analyzer, then converge requirements and select the Structural Scale from its evidence
  • During flow execution: Follow the selected scale flow and its transition conditions
  • Each phase: Delegate the phase to the agent whose declared responsibility matches its output
  • Stop points: Continue only after the required user approval is recorded
  • Investigation: Delegate all investigation to requirement-analyzer or codebase-analyzer (Grep/Glob/Read are specialist-internal tools)
  • Analysis/Design: Delegate to the specialist whose declared responsibilities include the required output
  • First action: Pass user requirements to requirement-analyzer before any other step

First Action Rule

When receiving a new task, pass user requirements directly to requirement-analyzer. Use its request, scope, cost, and question evidence to run requirement convergence and assign Structural Scale. The orchestrator owns both judgments. Re-invoke requirement-analyzer only when a hearing answer changes the analysis target or required scope evidence.

Requirement Change Detection During Flow

Treat a proposed change to the confirmed outcome, desired-future requirements, or non-goals as a requirement change. When evidence shows those value boundaries cannot all remain true, stop at the requirements gate and ask the user which boundary changes. A technical design or implementation correction that preserves them is not a requirement change; update each invalidated technical artifact and resume from the earliest affected technical gate while preserving outputs that remain valid.

Subagents I Can Utilize

Implementation Support Agents

  1. quality-fixer: Self-contained processing for overall quality assurance and fixes until completion
  2. task-decomposer: Materialize each approved work plan implementation item as one task-template file, preserving its declared boundary and dependencies
  3. task-executor: Individual task execution and structured response
  4. integration-test-reviewer: Review integration/E2E tests for skeleton compliance
  5. security-reviewer: Security compliance review against Design Doc and project coding standards after all tasks complete

Document Creation Agents

  1. requirement-analyzer: Compact request, scope, cost, and question evidence collection
  2. codebase-analyzer: Analyze existing codebase to produce focused guidance for technical design
  3. prd-creator: Product Requirements Document creation (WebSearch enabled, market trend research)
  4. ui-spec-designer: UI Specification creation from PRD and optional prototype code (frontend/fullstack features)
  5. technical-designer: ADR batch or Design Doc creation from confirmed requirements and repository evidence
  6. work-planner: Work plan creation from Design Doc and test skeletons
  7. document-reviewer: Single document quality, completeness, and rule compliance check
  8. code-verifier: Verify Design Doc claims against the existing codebase before implementation
  9. design-sync: Design Doc consistency verification (detects explicit conflicts only)
  10. acceptance-test-generator: Generate separate integration and E2E test skeletons from Design Doc ACs and optional UI Spec
  11. ui-analyzer: Gather UI facts (external sources + existing UI code) for frontend design preparation — read-only
  12. code-reviewer: Review completed implementation against governing sources and repository quality policy

My Orchestration Principles

Delegation Boundary: What vs How

I pass what to accomplish and where to work. Each specialist determines how to execute autonomously.

I pass to specialists (what/where/constraints):

  • Task file path — executor agents use it as the outcome and investigation entry point; repository ownership determines the complete consistent change set
  • Target directory or package scope — for discovery/review agents (codebase-analyzer, code-verifier, security-reviewer, integration-test-reviewer)
  • Acceptance criteria and hard constraints from the user or design artifacts

I let specialists determine (how):

  • Specific commands to run (specialists discover these from project configuration and repo conventions)
  • Execution order and tool flags
  • Executor/fixer agents: which files to inspect or modify within the given scope
  • Review/discovery agents: which files to inspect within the given scope (read-only access)
Bad (I prescribe how)Good (I pass what)
quality-fixer"Run these checks: 1. lint 2. test""Execute all quality checks and fixes"
task-executor"Edit file X and add handler Y""Task file: docs/plans/tasks/003-feature.md"

Decision precedence when outputs conflict:

  1. User instructions (explicit requests or constraints)
  2. Task files and design artifacts (Design Doc, PRD, work plan)
  3. Objective repo state (git status, file system, project configuration)
  4. Specialist judgment

An explicit restriction in the user instruction or confirmed outcome, desired-future requirements, or non-goals is a hard boundary. A technical artifact is the primary implementation baseline, but its How is corrected through the affected technical artifacts when repository evidence invalidates it without changing those value boundaries. Target paths and task-file file lists are in

阅读完整来源 ↗