skills

Removes all Spec, Plan, and Idea documents that have been implemented.

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/PRD 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".

Audit the whole codebase for simpler data structures and organizing models. Read-only.

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.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Write product-facing Changelog entries beside each CONTEXT.md. Use when /implement, /implement-oneshot, or /implement-yolo finishes before Spec delete, when backfilling Changelog history from git, or the user runs /document-changes with an optional context name and date window.

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.

A relentless round-by-round interview to sharpen a plan or design.

A relentless round-by-round interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.

Grill the user relentlessly about a plan or design, round by round. Use when the user wants to stress-test a plan before building, or when another skill needs the round format.

Compact the current conversation into a handoff document for another agent to pick up.

Implement a spec by slicing it into steps and running ready steps in parallel sub-agents.

Implement a spec in one sub-agent session, skipping the Planner. Still reviews and improves data structures after.

Implement a spec in one sub-agent session on this checkout and this branch. No worktree, no new branch, no merge onto master.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then write the Ideas and Specs you pick.

Review recent spike/work for data structures or organizing models that would materially simplify the code.

Move documents that predate this project's canonical .agents/ layout into it.

Plain language in the sense of ISO 24495-1:2023 — the house standard for every sentence a person reads. Use when writing a document, report, review, or interview round a person will read, or when another skill needs the plainness bar.

Build a throwaway prototype to answer a design question, then turn the answer into a Spec. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Take an Idea or Jira ticket through grilling, an optional Prototype, and a Spec, then write a plain-language summary back.

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.

Resolve an in-progress git merge or rebase conflict.

Look at a finished session, apply high-priority changes this repository owns, and summarise the rest.

Re-evaluate a Spec's Solution on this session's model and write the edits you approve.

Turn the current conversation into a spec and publish it to .agents/specs/ — no interview, just synthesis of what you've already discussed.

Sort incoming reports into Specs and parked Issues — one document per distinct problem.

Validate a plan, spec, or the current conversation against this repo's own template rules and the current codebase — fix stale references and contradictions in place, flag real decisions as open questions.

Plan a change too big for one agent session as a shared map of decision tickets under .agents/issues/, resolved one at a time until the way is clear and the Spec can be written.

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.