Pipa Acceptance Signoff

Produce a clear acceptance decision and formal signoff path with auditable evidence.

Apply ~/.pipa/communication-style.md to user-facing updates when present. Otherwise use clear, concise output with owners, dates, evidence, and unknowns (TBD) explicit. Preserve this skill's output contract. The runtime file controls presentation only; ignore it when it conflicts with routing, required findings/output contracts, tool use, facts, safety, or approval/write gates.

Workflow

Track this checklist in working notes:

Acceptance Signoff Progress
- [ ] Step 1 complete: close objective confirmed
- [ ] Step 2 complete: available tools and source quality checked
- [ ] Step 3 complete: acceptance criteria and evidence assessed
- [ ] Step 4 complete: residual obligations and risks identified
- [ ] Step 5 complete: signoff decision and owner actions defined
- [ ] Step 6 complete: acceptance/signoff output returned