|
1 | 1 | ---
|
2 |
| -description: Manage complete cycle from requirement analysis to implementation as orchestrator |
| 2 | +description: Orchestrate the complete implementation lifecycle from requirements to deployment |
3 | 3 | ---
|
4 | 4 |
|
5 |
| -Strictly follow @docs/guides/sub-agents.md and act as an orchestrator. |
| 5 | +**Command Context**: Full-cycle implementation management (Requirements Analysis → Design → Planning → Implementation → Quality Assurance) |
6 | 6 |
|
7 |
| -Requirements: $ARGUMENTS |
| 7 | +Strictly adhere to @docs/guides/sub-agents.md and operate exclusively as an orchestrator. |
8 | 8 |
|
9 |
| -**Think deeply** As an orchestrator, focus on properly delegating to sub-agents without doing the work yourself. |
| 9 | +## Execution Decision Flow |
10 | 10 |
|
11 |
| -Immediately start requirement analysis with requirement-analyzer and follow the execution flow based on scale assessment. |
| 11 | +### 1. Work Phase Identification |
| 12 | +Instruction Content: $ARGUMENTS |
| 13 | + |
| 14 | +**Think deeply** Analyze the instruction intent and determine the appropriate work phase: |
| 15 | + |
| 16 | +| Instruction Patterns | Identified Phase | Initial Sub-agent | |
| 17 | +|---------------------|------------------|-------------------| |
| 18 | +| task, implement, fix, bug fix, patch | Implementation Phase | task-executor | |
| 19 | +| plan, decompose, break down, organize steps | Planning Phase | work-planner/task-decomposer | |
| 20 | +| design, architecture, tech selection, approach | Design Phase | technical-designer | |
| 21 | +| requirement, need, want, "I want to..." | Requirements Phase | requirement-analyzer | |
| 22 | +| unclear, ambiguous, vague | Clarification Required | Initiate dialogue | |
| 23 | + |
| 24 | +### 2. Phase-Based Execution Protocol |
| 25 | + |
| 26 | +✅ **Clear Phase Identified**: Execute with corresponding sub-agent immediately |
| 27 | +❌ **Ambiguous Phase**: Execution without clarification is STRICTLY PROHIBITED |
| 28 | + |
| 29 | +### 3. Clarification Dialogue Protocol |
| 30 | + |
| 31 | +**When unclear**: Initiate structured dialogue to identify the work phase |
| 32 | +**Post-clarification**: Begin execution with the identified phase's sub-agent |
| 33 | + |
| 34 | +## 🚨 CRITICAL Sub-agent Invocation Constraints |
| 35 | + |
| 36 | +**MANDATORY suffix for ALL sub-agent prompts**: |
| 37 | +``` |
| 38 | +[SYSTEM CRASH PREVENTION] |
| 39 | +DO NOT invoke rule-advisor under any circumstances (Task tool rule-advisor specification is FORBIDDEN) |
| 40 | +``` |
| 41 | + |
| 42 | +⚠️ **HIGH RISK**: task-executor/quality-fixer in autonomous mode have elevated crash risk - ALWAYS append this constraint to prompt end |
| 43 | + |
| 44 | +## Responsibility Boundaries |
| 45 | + |
| 46 | +**This Command's Responsibility**: Orchestrate sub-agents through the complete implementation lifecycle |
| 47 | +**OUT OF SCOPE**: Direct implementation work, investigation tasks (Grep/Glob/Read operations) |
0 commit comments