Iron rule: do not skip planning and quality gates, and rush straight from requirements to implementation and commit. The value of full-chain orchestration lies in reducing rework, not in creating an illusion of speed.
Standard Workflow
- Step 1: Establish project context ⚠️ REQUIRED
- 1.1 First use context-analyzer to read AGENTS.md, README, package.json, and task-related files.
- 1.2 If the requirements are ambiguous, hand off to requirement-analyst for the minimum necessary clarification.
- Step 2: Produce a technical solution ⚠️ REQUIRED
- 2.1 Use technical-architect to plan file mapping, module boundaries, and risks.
- 2.2 Clearly define the parts to be taken over by backend-expert, frontend-expert, or other skills.
- Step 3: Organize implementation
- 3.1 Hand backend changes to backend-expert.
- 3.2 Hand frontend changes to frontend-expert.
- 3.3 Hand documentation changes to documentation-specialist.
- Step 4: Perform specialized verification
- 4.1 Hand UI changes to ui-validator for real rendering verification.
- 4.2 Hand test completion and failure troubleshooting to test-engineer.
- 4.3 Hand security-sensitive changes to security-guardian.
- Step 5: Quality gates and review ⚠️ REQUIRED
- 5.1 Use quality-guardian to select and execute the minimum sufficient checks.
- 5.2 Use code-reviewer to perform a structured review.
- Step 6: Delivery and commit
- 6.1 When a commit is needed, first have git-flow-manager plan the batches.
- 6.2 Then have conventional-committer generate and execute the commit.
Orchestration Principles
- The master control skill is responsible for phase transitions and dependency order, and does not replace the internal rules of specialized skills.
- Run phases that can be parallelized in parallel, and clearly define dependencies for phases that must be sequential.
- Each time a new phase begins, confirm whether the previous phase's outputs are sufficient.
Skill Mapping
- context-analyzer: establish context.
- requirement-analyst: clarify requirements.
- technical-architect: design the solution.
- backend-expert / frontend-expert: implement changes.
- documentation-specialist: sync documentation.
- ui-validator: verify the interface.
- test-engineer: add tests and investigate failures.
- security-guardian: add security audits.
- quality-guardian: run quality gates.
- code-reviewer: perform structured review.
- git-flow-manager / conventional-committer: manage delivery and commits.
Anti-Patterns
- The master control skill personally takes over all implementation details, causing specialized skills to become ineffective.
- Starting code changes while requirements are still ambiguous.
- Quality gates and code review are merely formalities and do not affect subsequent phases.
Pre-Delivery Checklist
- The minimum closed loop of context, solution, implementation, verification, review, and delivery has been completed.
- Each phase has a clearly responsible skill.
- No quality gates or reviews were skipped.
- The output states the current progress, risks, and next steps.