finish-card

Validate Definition of Done criteria and append closure entries to log.md.

6|Updated May 4, 2026
One-click install
npx skills add https://github.com/zauberzeug/game-of-cards --skill finish-card
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-card
Source: https://github.com/zauberzeug/game-of-cards/tree/main/openclaw-plugin/skills/finish-card
Command: npx skills add https://github.com/zauberzeug/game-of-cards --skill finish-card

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Card closures can be risky without a machine-checked Definition of Done. This skill enforces a DoD-driven closure workflow for cards and ensures closure details are recorded in log.md for auditability and handoff.

Core Features & Use Cases

  • Enforce the DoD-driven closure contract and prevent closing unless all criteria are ticked.
  • Append a closure narrative to log.md including audit outcomes and verification notes.
  • Trigger project-specific post-close actions via repository hooks and the GoC workflow (attest/done).
  • Use Case: When a card reaches done status, the system prevents premature closure and records the closure.

Quick Start

Close a card by validating all DoD criteria and append a closure log entry to log.md.

Frequently Asked Questions about finish-card

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

FAQPage Schema
How do I enforce a Definition of Done before closing project cards?

To prevent premature card closures, a DoD-driven workflow validates each Definition of Done criteria before allowing a card to reach done status. It blocks transitions unless all specified DoD checklist items are successfully ticked and verified.

How do I automatically update log.md when closing agile cards?

Automatically updating log.md when closing agile cards requires appending a closure narrative after DoD validation. The system records audit outcomes and verification notes directly into the log to ensure project handoff readiness and continuous auditability.

Does the GoC workflow support automated post-close hooks for project management?

Yes, the GoC workflow supports automated post-close hooks for project management. It integrates with goc attest and goc done commands to trigger repository-specific actions immediately after a card successfully passes its Definition of Done validation.

Can I use card-workflow automation to satisfy project rubric audits?

Yes, you can use card-workflow automation to satisfy project rubric audits. The enforcement of a DoD-driven closure contract and the systematic recording of verification notes in log.md provide the necessary auditability and compliance evidence.

Why does my card closure fail when using a DoD-driven workflow?

Card closure fails in a DoD-driven workflow when the validation process detects incomplete criteria. The system intentionally prevents closing a card by blocking the done transition until every required Definition of Done checkbox is ticked.