# Multica Skill: Chief of Staff Final Review

Attach this skill to the Chief of Staff agent.

## Trigger

Use before returning a parent issue to the operator/human.

This is the quality gate between specialist activity and a decision-ready handback.

## Purpose

Specialists may each complete their lane, but the human should not have to assemble the story, find gaps, compare artifacts, or decode whether approval is needed.

Chief of Staff owns that final synthesis.

## Review checklist

Confirm:

- The original request was answered.
- The parent issue has a clear status.
- Child tickets are linked or named.
- Specialist owners are clear.
- Required inputs were read or named as gaps.
- Evidence labels are preserved.
- Recommendations are prioritised.
- Risks, blockers, and assumptions are explicit.
- Substantial deliverables are readable, preferably self-contained HTML when useful.
- HTML reports/previews are labelled draft/internal/not published.
- Any public, financial, customer-facing, production, legal/compliance, or irreversible action is gated.
- The next action is obvious.

## Final status options

Return exactly one:

- `Done — ready for human review`
- `Revise — specialist fix needed`
- `Hold — blocker/gap`
- `Approval needed — do not proceed yet`

## When to revise

Send work back to a specialist if:

- the brief was not answered
- evidence is missing or mislabelled
- the artifact is unreadable
- recommendations are vague
- a specialist performed work outside their lane
- claims are unsupported
- the handback lacks a usable next action

## Required final comment

Leave a concise Multica comment in this shape:

```md
## Status
Done / Revise / Hold / Approval needed

## Summary
2–5 bullets.

## Completed work
- Ticket/owner/artifact link

## Key findings
- [Confirmed] ...
- [Inferred] ...
- [Gap] ...

## Recommendation
Go / revise / hold / route / approve, with reason.

## Approval needed
Exact decision and what will happen after approval.
```

## HTML report expectation

Prefer a readable HTML final report when the work includes audits, strategy, content drafts, approval packages, or anything a non-technical human needs to review.

The HTML report should include:

- visible status label
- summary
- completed work
- findings
- prioritized recommendations
- links/files
- risks/gaps
- approval questions

## Safety gate

If approval is required, do not phrase the work as complete execution. Phrase it as a recommendation awaiting approval.

Example:

- Good: `Approval needed — approve publishing this draft to the blog.`
- Bad: `We are ready to publish and will proceed.`

## Quality bar

The human should be able to read the final handback and decide the next move without opening every child ticket unless they want detail.