
Use when deciding between two approaches and you need a structured tradeoff comparison
- Open source
- 14 GitHub stars

Use when deciding between two approaches and you need a structured tradeoff comparison

Use when you want to browse available skills or find the right pipeline for a workflow






Use when multiple agents or skills produced separate findings that need combining into one list



Use when you've decided on an approach and need to see the structure before implementing

Use when items need reformatting without changing the collection (e.g., as ticket titles, test cases, or for a different audience)

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