buaflow

Check finished work before asking a human to approve. Runs verify for real, compares the diff to the plan, then hands the diff to the built-in /code-review and /security-review. Use after /task and before /done. Not named /review because that collides with the built-in alias.

Close a task that passed /check and was approved by the user. Marks the PR ready for review (never merges), updates the task file, regenerates the board, unblocks waiting tasks, and feeds lessons back into config.

Work out what a thin requirement leaves out before it is specced — the goal behind the ask, what the business domain normally needs around it, and what the system already has — then research it and propose additions for the user to decide. Use after /intent when the brief is open (the customer gave the main features and expects us to think the rest through), before /spec.

Urgent production fix procedure — record the symptom, find the cause, choose the approach, fix, release, then postmortem and feed back into the system.

Open new work by capturing "why" before "what". Use for an idea, a problem, a user request, a postmortem outcome, or a Sonar finding that has not yet been decided on. Tiny work (typo/copy/log) uses the trivial track instead.

Plan before touching code and save it as plan.md that distills every requirement this task needs into one file, so /task and /check read one file only. Use for work that changes several files, unfamiliar code, or risky tasks.

Build or refresh a click-through prototype from the committed canvas baseline (docs/design/canvas/*.dc.html) plus a hotspot/data map, then publish it as a shareable link for the team or customer. Use after a canvas is confirmed, and every time the baseline changes.

Release to uat or prd — run the milestone gate, build the image once, tag, prepare the release note and rollback plan. Use when closing a milestone, not per task. Works before a deploy target exists.

Spec a large feature as requirements, design, and tasks with an approval gate between each. Use when an intent has been accepted and the work is big enough to need a spec.

Start or resume Buaflow in this project from the plugin — a new project, an existing codebase, or one that already has Buaflow installed. Use when the user asks to start Buaflow, set it up, or continue it. Upgrading the installed controls is /buaflow:upgrade.

Pick a task from the backlog and work it. Pass an ID or leave empty to get suggestions. Covers choosing the task, confirming understanding, implementing, and self-checking before /check.

Start building a UI component or screen by asking first, never designing on your own. Offers text or canvas (claude.ai/design) when no design exists, then builds to match the design exactly. Use every time before creating a component or screen.

Upgrade the Buaflow controls installed in this project (the gate, checkers and lock in .claude/) to the plugin's kit, from any earlier version, including a project installed before the lock existed or by copying the kit into .claude/. Use when the user asks to upgrade Buaflow, or the session notice says the project is behind the plugin.