
Use when prior findings contain claims that need fact-checking against code, docs, or reality
- Open source
- 14 GitHub stars

Use when prior findings contain claims that need fact-checking against code, docs, or reality

Use when you need to research, analyze, compare, plan, or structure thinking and aren't sure which primitive to reach for

Use when an agent's performance is uneven and you want systematic improvement

Use when starting a project, forming a team for long-horizon work, or upgrading from ad-hoc agent dispatch

Use when learnings feel bloated, before sprints, after /retro, or when rules need a health check

Use after /curate or /retro when learnings have accumulated and you want to graduate durable patterns to project rules

Use at the end of a work session, after completing an epic, or when you want to capture what worked and what didn't


Use when a team exists but current status is unknown — backlog changed, context switch happened, or session just started

Use when you have a goal and want the team to plan it collaboratively — not explore (blossom) or brainstorm (meeting)




Use when starting a new project or adding Claude Code support to an existing one


Use after /diagnose-agent when you have a struggle profile and need training challenges

Use after /challenge-gen when challenges are ready to execute

Use when torn between architectural approaches or when you suspect hidden trade-offs

Use when the backlog feels unwieldy — after a blossom run, before a sprint, or when you suspect duplicates or stale tasks

Use when code is ready to ship and you want a structured deployment with readiness checks and rollback criteria

Use when an agent's performance is uneven and you want to understand where it excels or struggles

Use when a term is ambiguous or project-specific and needs a canonical definition


Use when you have a plan document and want autonomous implementation until it's done

Use when reviewing a skill/agent/rule and you need to understand why it looks the way it does


Use when you need deep understanding of a focused area — not broad exploration

Capture the orchestrator's mental model for a structured session transition

Use after parallel bounded-context implementation to verify contracts still hold

Use when you need multiple perspectives on a topic — brainstorming, requirements clarification, or pressure-testing an idea before committin