Skip to content

Skills

Each page below explains one skill: what it is for, when to use it and when to use another, how to start it, what it produces, and where it can stop. Pick a skill by the task in front of you; the domain headings only group the list. For how skills pass work to each other, read How skills hand work to each other. For what the domains mean, read How the suite works.

Each page also says why the skill is built the way it is: the failure it exists to prevent, what it deliberately refuses to do, and how it helps a weaker agent without holding back a stronger one. Those reasons come from the project owner's stated intent for each skill, most of it recorded in issue #3. The principle they share is in the skill design philosophy.

Workbench

  • Architect: decide a structural question, such as a boundary, dependency direction, or module structure, before planning.
  • Assess: review one exact change against its requirements and base behavior before you trust it.
  • Blueprint: plan a repository change so completely that a weaker agent can carry it out.
  • Charter: give a rough idea for a whole project its agreed purpose, scope, and success before anyone splits it into tickets.
  • Construct: carry out a sealed Blueprint plan and verify the result.
  • Diagnose: find the evidence-backed cause of a defect, risk, or improvement opportunity before anyone decides a fix.
  • PR: write a reviewer-oriented pull request description and open the pull request, or update its description, once you confirm it.
  • Provision: install the suite's Python requirements and set up its subagents on the models you choose.
  • Ticket: split large work into session-sized tickets, or pick the next ready ticket and prepare it for planning.

Sensemaking

  • Ideate: research and compare options for a goal and recommend a direction you choose from.
  • Reason: check a judgment at the moments it matters, or ask what only you can answer.
  • Router: lay out which skills to use, in what order, as far as that can be known now.
  • Scribe: write or audit technical documentation that carries its sources faithfully.

Learning

  • Examiner: write practice papers for a specific written examination and mark attempts.
  • Tutor: learn any subject through an explanation, interactive tutoring, or a continuing series.