workflow

Conduct an independent review of a change, keyed to the plan's acceptance criteria. Use when reviewing a PR (locate the plan folder via its `Workflow-Plan:` marker) or after local plan execution. Fixes straightforward findings in place and authors remediation briefs for structural ones; reconstructs intent for a no-plan PR.

Execute an existing plan from `docs/plans/`. Use when the user wants to implement a planned work package — routing `refine`'s briefs to workers (or authoring one inline for single-worker slices), tracking implementation progressively, and running review sized to the declared posture.

Create or revise implementation plans for this repo. Use when a user asks for a plan, to restructure plan docs, or to define a self-contained work package with clear contracts and acceptance criteria.

Orchestrate the post-build pipeline stage against a PR produced by execute — independent review with in-place fixes, remediation only for briefed structural findings, conditional QA with exact-SHA deploy proof, a single end-of-work required-checks gate, and a merge-readiness report. Right-sizes the stage to change classification (plan presence, functional surface, size). Use when picking up a PR after the build stage, or when an automation triggers the post-build workflow.

Turn an approved plan into executable work — decompose it into ordered units and write one complete brief per unit into the plan folder, or report that the plan cannot support briefs yet. Use between `plan` and `execute` when the work is more than one worker can carry.