Choose a skill
Start from the problem in front of you, not from how the suite is organized. Pick the smallest skill that deals with what is most likely to cost you time later. A small, clear request may need no skill at all.
Find your situation
| You are dealing with | Start with |
|---|---|
| Something is wrong and you do not know why | Diagnose |
| A change another session, agent, or cheaper model will carry out, whose mistakes would show up late, or whose decisions must outlast the session | Blueprint |
| A sealed Blueprint plan that is ready to carry out | Construct |
| A structural question, such as a boundary, dependency direction, or module structure | Architect |
| A finished change you need to trust before merging | Assess |
| A rough idea for a whole app or project whose purpose, scope, and success are not agreed yet | Charter |
| Work too big for one session, or a backlog to pick the next ready ticket from | Ticket |
| Several possible directions and no clear way to choose | Ideate |
| A decision that is stuck, or rests on an assumption you doubt | Reason |
| Not knowing which skill comes next, or work that spans several skills | Router (ask in plain words) |
| A runbook, setup guide, error message, or other technical document that must match its sources, or a check of an existing one | Scribe |
| A subject you want to understand | Tutor |
| A written examination to practise for | Examiner |
| A fresh install to finish, or subagents to set up or refresh on the models you choose | Provision |
The table covers common situations, not every skill; the skill index lists every skill, and each skill page says when to use another skill instead.
Combine skills only when you need to
Every skill works alone. A skill's handoff makes the next step possible, but never starts it. When one skill is not enough, for example:
- Diagnose finds a cause, then Blueprint plans a fix for one finding and Construct carries out the plan. When that fix first needs a structural decision, Architect settles it before Blueprint.
- Architect settles structure, then Blueprint plans around it.
- Charter settles what a project is for, then Ticket splits it into tickets.
- Ticket narrows one ready ticket, then Blueprint plans it.
- Assess findings go to a new Blueprint run rather than a direct edit.
- Tutor and Examiner can share one study plan for a subject.
How skills hand work to each other describes each real handoff.
How the skills are grouped
The skills are grouped into three domains, Workbench, Sensemaking, and Learning, to help you understand the suite. The grouping is not a step in choosing. See How the suite works and the skill index.