AgentSkillsCN

orchestrate

重申需求、评估风险,并制定分步实施计划。在触碰任何代码之前,务必等待用户的确认。

SKILL.md
--- frontmatter
name: orchestrate
description: Sequential agent workflow for complex tasks
user-invocable: true
disable-model-invocation: true
context: fork

Orchestrate Command

Sequential agent workflow for complex tasks.

Usage

/orchestrate [workflow-type] [task-description]

Workflow Types

feature

Full feature implementation workflow:

code
planner -> tdd-guide -> code-reviewer -> security-reviewer

bugfix

Bug investigation and fix workflow:

code
explorer -> tdd-guide -> code-reviewer

refactor

Safe refactoring workflow:

code
architect -> code-reviewer -> tdd-guide

security

Security-focused review:

code
security-reviewer -> code-reviewer -> architect

Execution Pattern

For each agent in the workflow:

  1. Invoke agent with context from previous agent
  2. Collect output as structured handoff document
  3. Pass to next agent in chain
  4. Aggregate results into final report

Handoff Document Format

Between agents, create handoff document:

markdown
## HANDOFF: [previous-agent] -> [next-agent]

### Context
[Summary of what was done]

### Findings
[Key discoveries or decisions]

### Files Modified
[List of files touched]

### Open Questions
[Unresolved items for next agent]

### Recommendations
[Suggested next steps]

Final Report Format

code
ORCHESTRATION REPORT
====================
Workflow: feature
Task: Add user authentication
Agents: planner -> tdd-guide -> code-reviewer -> security-reviewer

SUMMARY
-------
[One paragraph summary]

AGENT OUTPUTS
-------------
Planner: [summary]
TDD Guide: [summary]
Code Reviewer: [summary]
Security Reviewer: [summary]

FILES CHANGED
-------------
[List all files modified]

TEST RESULTS
------------
[Test pass/fail summary]

SECURITY STATUS
---------------
[Security findings]

RECOMMENDATION
--------------
[SHIP / NEEDS WORK / BLOCKED]

Arguments

$ARGUMENTS:

  • feature <description> - Full feature workflow
  • bugfix <description> - Bug fix workflow
  • refactor <description> - Refactoring workflow
  • security <description> - Security review workflow
  • custom <agents> <description> - Custom agent sequence

Tips

  1. Start with planner for complex features
  2. Always include code-reviewer before merge
  3. Use security-reviewer for auth/payment/PII
  4. Keep handoffs concise - focus on what next agent needs
  5. Run verification between agents if needed