菜单
Use when executing implementation plans with independent tasks in the current session
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when managing the Claude CLI Proxy (ban protector) — start, stop, restart, status, logs, backup, test, setup, or register the proxy in OpenClaw. Triggers on: 'proxy status', 'ban protector', 'start proxy', 'stop proxy', 'proxy health', 'antiban', 'cli proxy'.
Run stateful multi-agent graph workflows using LangGraph (linear, supervisor, parallel, conditional). Use when tasks need dynamic routing, branching logic, or a supervisor agent delegating work. All LLM calls use OpenClaw's existing provider config — no API keys needed. Choose over autogen-collab (debate) and crewai-collab (fixed pipelines) when you need conditional edges, a supervisor making routing decisions, or parallel fan-out with synthesis.
Run multi-agent AutoGen-style debates when tasks need consensus across specialists. Uses OpenClaw's existing provider configuration — no API keys or extra setup needed. Use when: architecture decisions, design reviews, root cause analysis, or complex research where multiple expert perspectives improve the answer. Triggered automatically by Cooper for high-complexity tasks or explicitly via [autogen] tag or "debate this" / "get consensus" instructions.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Run structured multi-agent workflows using CrewAI (sequential, hierarchical, consensus). Each agent has a defined role, goal, and backstory. Tasks have explicit expected outputs. Use when: structured pipelines (research → design → implement), manager-supervised workflows, or consensus-building with clear acceptance criteria. All LLM calls use OpenClaw's existing provider config — no API keys needed.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
| name | subagent-driven-development |
| description | Use when executing implementation plans with independent tasks in the current session |
| metadata | {"openclaw":{"emoji":"⚙️"}} |
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
vs. Executing Plans (parallel session):
references/implementer-prompt.md)references/spec-reviewer-prompt.md)references/code-quality-reviewer-prompt.md)references/implementer-prompt.md - Dispatch implementer subagentreferences/spec-reviewer-prompt.md - Dispatch spec compliance reviewer subagentreferences/code-quality-reviewer-prompt.md - Dispatch code quality reviewer subagentvs. Manual execution:
Quality gates:
Never:
If subagent asks questions:
If reviewer finds issues:
Required workflow skills:
Subagents should use:
Alternative workflow: