Menu
Route work through bounded subagents. Use when tasks require codebase investigation, code changes, tests, lint, build, or multi-step validation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use for GitHub operations: creating issues, posting issue comments, creating draft PRs, and adding PR review comments.
Facilitate structured divergent idea generation using the SCAMPER technique (Bob Eberle). An orchestrator elicits a concrete target, applies seven transformation lenses (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse) in parallel via focused subagents, then converges into evaluated, prioritized ideas. Use when the user asks for a SCAMPER analysis, systematic ideation, or improvement ideas for an existing product, service, process, or idea.
Facilitate structured multi-perspective analysis using Edward de Bono's Six Thinking Hats. A Blue Hat orchestrator applies one hat at a time in sequence over a single shared record, using five focused hat subagents. Use when the user asks for a Six Hats or 6 hat analysis, a multi-perspective breakdown of a decision, idea, or problem, or systematic structured thinking on a topic.
Author markmap-format Markdown. Use when writing a mindmap (マインドマップ / markmap) in Markdown.
Sample skill for verifying plugin wiring. Trigger when the user asks to run the sample greeting or test the sample plugin.
Use when resolving or addressing PR review comments.
| name | subagent-first |
| description | Route work through bounded subagents. Use when tasks require codebase investigation, code changes, tests, lint, build, or multi-step validation. |
Main agent = orchestrator only.
It plans, routes, reviews concise results, and decides next step.
It does not read implementation files, implement, run tests, lint, or build.
It may read planning and design artifacts (plan files, ADR, docs/) directly for routing context.
Use separate subagents for these phases:
Every subagent prompt must include:
Subagents return only:
status: success | failure | blocked
summary:
files_changed:
log_path:
next_action:
Verbose output goes to docs/tmp/.
After each subagent result, main agent must choose exactly one: