diagnosing-bugs /diagnosing-bugs Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
domain-modeling /domain-modeling Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
grill-with-docs /grill-with-docs A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. disable-model-invocation: true
to-prd /to-prd Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed. disable-model-invocation: true
work-on-issues /work-on-issues > Fetch, implement, and close GitHub/GitLab issues sequentially (one main issue starting with PRD:/feat: at a time). Handles parallel subtasks, dependency parsing, worktrees, and env propagation.
codebase-design /codebase-design Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
to-issues /to-issues Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. disable-model-invocation: true
ask-utarn /ask-utarn Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo. disable-model-invocation: true
implement /implement Implement a piece of work based on a spec or set of tickets." disable-model-invocation: true
find-mismatch /find-mismatch > Systematic code review focusing on bugs that break at runtime (contract mismatches, logic/async errors, serialization, styling) and JS/TS static analysis via fallow. disable-model-invocation: true
improve-codebase-architecture /improve-codebase-architecture Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. disable-model-invocation: true
resolving-merge-conflicts /resolving-merge-conflicts Use when you need to resolve an in-progress git merge/rebase conflict.
setup-utarn-skills /setup-utarn-skills Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills. disable-model-invocation: true
prototype /prototype Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
tdd /tdd Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
triage /triage Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs. disable-model-invocation: true
to-issues-yes /to-issues-yes Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. disable-model-invocation: true
code-review /code-review Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
research /research Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
to-spec /to-spec Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed. disable-model-invocation: true
to-tickets /to-tickets Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker. disable-model-invocation: true
to-tickets-yes /to-tickets-yes Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker. disable-model-invocation: true
wayfinder /wayfinder Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear. disable-model-invocation: true
grill-novice /grill-novice A grilling session that asks you only the functional requirements, in plain simplified English, while the agent settles every technical detail itself and recaps the assumptions for your veto before anything is written. disable-model-invocation: true
