Aiwork

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 requirements, specs, or tickets. Detect input (pasted text, markdown path, tracker ticket id/URL, or empty prompt). Explore codebase + docs, score completeness, ask clarifying questions, write a markdown report. Trigger when user says "triage", "review this spec", "is this requirement complete", or provides a ticket/spec to assess.

Turn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.

Implement a single ticket or a small inline change in one pass, in this session.

Build a throwaway prototype that answers one design question. Plain HTML/CSS/JS in the task's .aiwork/ folder by default, or UI variants inside the app (Nuxt/Vue, ...) on a prototype branch when they must sit against real layout and data. Use for "does this state model feel right" or "what should this look like".

Stop — that last message did not land. Re-pitch it in plain language.

Break a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.

Implement a whole spec by orchestrating subagents over its ticket graph; auto-detects the most recent task folder when no argument is given.

Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (intent, triage, research, spec, prd, areas, plan, review, notes, docs/). Use when the user asks to plan, capture an intent, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.