PBI Retrospective

Status: Experimental

This skill gives the team a consistent, evidence-backed closeout review for a non-trivial PBI, ticket, release, or delivery. It is intentionally read-only: it reports whether the work is safe to close and names follow-ups without changing a tracker, repository, or deployment.

When To Use

• “Review PBI 12345 before we close it.”
• “Run a retrospective on this release and identify the remaining evidence.”
• “Is this work actually ready to mark Done?”

Requirements

• The relevant repository, work-item evidence, and acceptance criteria must be in the current task scope.
• No tracker, source-control, cloud, or deployment access is required for a report-only review.
• Any external update, including a status change or follow-up ticket, requires separate user authorization.

Install

Try this skill intentionally while it is Experimental:

scripts/install-skill.sh pbi-retrospective codex
scripts/install-skill.sh pbi-retrospective copilot /path/to/project-repo
scripts/install-skill.sh pbi-retrospective cursor /path/to/project-repo

Typical Output

• Completion evidence, separated from unverified claims.
• Gaps, near-misses, and concise lessons.
• A closeout status: ready, not ready, or blocked.
• Proposed follow-ups; no external records are changed.

Testing

Dry run the skill against a completed sample ticket that has a passing test result but an open pull request. The result must mark the work not ready, identify the open pull request as missing terminal evidence, and make no external changes.

Also dry run a clean closeout with acceptance criteria, merged source changes, required validation, and user-facing verification. The result should mark it ready and avoid inventing follow-ups.

Example Prompt

Use $pbi-retrospective to review this completed PBI. Verify the acceptance criteria, pull-request state, validation evidence, and deployment record. Do not update the tracker or repository; return the closeout status and any follow-ups.