close-phase

Close a finished project phase with done-gates, retrospectives, and gated merges to main.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill close-phase-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-phase
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/close-phase
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill close-phase-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Wrapping up a finished development phase often loses decisions, follow-ups, and test evidence in chat scrollback, and half-finished work gets merged without verification. This Skill enforces a gated close-out: every story must be done, a retrospective is compiled from artefacts, follow-ups are filed, and the phase branch merges to main only after all gates pass. ## Core Features & Use Cases - Hard done-gate: Verifies every story in the target phase is marked done, aborting with a list of gaps if any are incomplete. - Artefact-derived retrospective: Compiles what shipped, what went well, metrics (bugs, ADRs, lanes), plus a recalled section from the retro ledger via retro-report.js. - Follow-up capture: Files BACKLOG items for tech debt and backstops missing ADRs so no decision is lost. - Gated integration: Detects already-merged branches via git ancestry, enforces a four-item merge gate (stories done, lint green, tests green, clean tree), then opens a PR or performs a gated direct merge, logging the approval to APPROVALS.md. - Use Case: After an execute-batch run finishes all stories in EPIC-12, ask to close the phase; the Skill writes the phase report to 41-Reports/phases/, updates MONITOR.md and the dashboard, and surfaces a PR link for the merge to main. ## Quick Start Close the phase for EPIC-12 now that all its stories are done, including the retrospective, board update, and gated merge to main.

Frequently Asked Questions about close-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I close a project phase after all stories are done?

Provide an explicit phase target such as a chat id, EPIC-NN, or FEAT-NN.M. The Skill resolves the stories, verifies each is done, compiles a retrospective, captures follow-ups, updates the board, and runs a gated merge to main.

What happens if some stories are not done when closing a phase?

The done-gate aborts the close and lists each not-done story with its current status. No retrospective, board update, or merge runs for an incomplete phase, so a half-closed phase is impossible.

Can I close a phase whose branch was already merged to main?

Yes. The Skill probes true ancestry with git merge-base --is-ancestor; if the phase branch is already reachable from main, it runs the retro-only path, skipping the merge but still completing the retrospective and board updates.

What conditions must pass before the phase merges to main?

Four gate items must all pass: every phase story is done, npm run pm:lint is green, build and tests pass per PROJECT-CONTEXT.md, and the git working tree is clean. Any failure blocks the merge and names the failing item.

Does closing a phase force-merge or require the GitHub CLI?

No. The Skill never force-merges and does not assume the gh CLI. It surfaces a copy-pasteable PR command or link by default, or performs a gated direct merge for solo workflows, then logs the approval to 10-Inbox/APPROVALS.md.