AkurAI-Build

public

Latest change e11509261b6a2aa4ea9ef67250b0be01bfb4f53b - Restore paths swept in from uncommitted WIP by Ólafur Búi Ólafsson

---
name: completion-review
description: "End-of-task evidence review that resolves work to done or blocked"
---

# Completion Review

# Kanban/Agile operating contract

Multica is system of record. Work is pull-based and bounded.

- `backlog`: unrefined demand only.
- `todo`: Definition of Ready passes: non-null project, linked repository or local-directory resource, bounded outcome, acceptance criteria, priority, owner/squad, known dependencies, and verification command or scenario.
- `in_progress`: one named owner actively executes. Ordinary members own one implementation item; squad leaders may additionally own one coordination parent.
- `blocked`: external dependency prevents next action. Link dependency or approval issue and state dated unblock condition.
- `in_review`: implementation evidence posted; @-mention a different agent for review.
- `done`: peer review, required immutable AkurAI-Build gates, integration smoke evidence, and applicable performance evidence pass.

Definition of Done requires acceptance evidence, no open blocking child/dependency, independent reviewer approval, successful immutable Build run when source changed, deployment/health evidence when runtime behavior changed, and Monitor baseline/regression evidence for request-serving Rust code.

Urgent incidents pre-empt only after current work returns to `todo` or is `blocked` with handoff comment. Do not self-review. Do not bypass review or evidence.

CI, deployment to current development VM, service restart, canary, rollback, and development data migrations are autonomous only after issue acceptance, review, backup/rollback, and health gates pass. Access or secret changes, public DNS, finance, external commitments, and any future production environment remain human-gated.

## Mandatory closing action
`in_review` is a transit state, never where a run ends. Terminal transitions go through the `multica` TOOL (not bash — raw `multica issue status/create` in bash is blocked by the autonomy guard). Before your task exits, call the multica tool:

action: issue_resolve, issue: <ISSUE-KEY>, status: done, comment: <evidence — what shipped, how verified, where the proof lives (>=40 chars)>

or, if a genuine external dependency prevents completion:

action: issue_resolve, issue: <ISSUE-KEY>, status: blocked, comment: <recovery attempts, the external prerequisite, and a dated unblock condition>

Non-terminal moves use action issue_status (backlog|todo|in_progress|cancelled). New issues use action issue_create with a project UUID. A run that ends with its issue still in `in_review` is a defect and will be nudged back to you.