← ClaudeAtlas

finish-cardlisted

Close a card with DoD enforcement, log.md closure entry, and project-specific post-close / commit handoff. AUTO-INVOKE when user says "done", "close this", "finish X", "mark complete", "wrap up", "ship it", or completes work that satisfies a card's DoD. The DoD checkboxes ARE the closure contract (Scrum Definition of Done) — `goc done` refuses to close with any unchecked.
zauberzeug/game-of-cards · ★ 2 · AI & Automation · score 75
Install: claude install-skill zauberzeug/game-of-cards
## Preflight If any `!` block below shows `goc: command not found`, `Permission for this action has been denied`, or `no such file or directory: .game-of-cards/deck/`, **stop and invoke `Skill(kickoff)` first**. Kickoff detects which setup step is missing (CLI not installed, Bash allowance not granted, project state not scaffolded) and walks the user through it. Re-invoke this skill only after kickoff completes. # Close a card Scrum's **Definition of Done** as a machine-checkable closure contract. The DoD is the agreement, set when the card was filed, that the work is actually complete — not "the test passed once," but every named criterion satisfied. An LLM agent reading the card at 3 AM in a /loop iteration must not be able to mark the work done by accident; the contract is enforced by `goc done`, which counts unchecked boxes and refuses to flip the status if any remain. The human-typed checkbox list is the audit trail. Closure is an eight-step contract — skip a step and the card is dishonest: 1. Verify the work satisfies the DoD criteria. 2. Run the project-specific closure audit (or honestly note that no project rubric applies). 3. Tick the DoD checkboxes in the README. 4. Append closure context to `log.md` (including the audit outcome). 5. Run `goc attest <title>` to record the Closure-verification block in `log.md` (layer-2 + layer-3 DoDs from `.game-of-cards/config.yaml`). 6. Run `goc done <title>` (DoD-100% gated). 7. Run any project-specific post-close action (s