Drive a feature from brief through specification, implementation, testing, and review while keeping publication as a separate explicit user decision.

Consume the issue or brief and requested profile. Invoke the base workflow and its lower-level companions by name; stop with the missing name if one is unavailable. Emit the staged handoff, optional / references, and final line. Publication is a separate human-authorized step.

ALWAYS check first: Apply when present; safety rules still win.

Follow to detect duplicate or in-flight work, resolve a trusted harness profile, create an isolated worktree from the configured base, and capture the harness start-state artifact before writing the spec.

Run in the isolated worktree. Resolve answerable open questions from repository evidence and surface only genuine product decisions. Use a repo-local when available. For , , and , follow the bound council contract: prepare an exact-spec packet, delegate to a new Claude context with no implementation transcript, and run every configured advisor concurrently on that same packet. Fix confirmed design blockers before implementation.

Implement the audited phases using the lower-level specification, test, and review skills named here. is the publication driver; reserve it for an explicitly authorized PR workflow because its normal engine creates commits and PRs. Do not invoke it inside this staged-only run. For profiles, dispatch bounded, file-disjoint packets through configured workers and verify every packet before integration. For , use versioned packet manifests and require blind review, fresh finding verification, separate fixer context, and deterministic exact-diff acceptance evidence before integration. Create no checkpoint commits.

Add unit and integration coverage for every changed behavior. Run when the repository supports it. Run the full configured validation gate. For UI changes, enforce the repository's design system on every touched UI line before review — run the repo-local design-system guardian skill when the repository ships one, otherwise apply its documented design-system rules and checklist — and run local without a PR number, keeping its artifacts outside the stage allowlist.

Run against the complete uncommitted implementation and spec. For and , create a new Claude context with no inherited implementation transcript and run the skill there. For , , and , follow the bound council contract: freeze the exact diff, validation evidence, and repository rules; start fresh Claude and every configured advisor concurrently with the same complete rubric and packet; then require Claude's matching artifact before reconciliation. Preserve minority findings, fix confirmed blockers, and repeat validation, packet preparation, and all reviews until no confirmed blocking finding remains or the loop reaches three iterations; then stop and report every surviving finding. Every configured council reviewer must complete: the runtime retries failures with backoff and timeout escalation, and a council missing any required reviewer yields no verdict — re-run it, repair the binding, or stop for the user's decision; never proceed on a partial council.

Follow the shared stage-only contract: supply the final implementation and approved artifacts even in mode, stage only intended files, assert refs and reflogs still match the captured start state, require a clean staged diff, render the report from , and stop for human review.

After capture, follow the stage-only contract to stop active processes and invoke on abort or terminal failure. Preserve files and packet leases for deliberate recovery. Keep the guard active while repairing or retrying the same run; successful staging ends it.