decklisted
Install: claude install-skill zauberzeug/game-of-cards
# The Deck
`deck/` is the project's work-tracking surface. Each subdirectory is one
**card**: a unit of work — bug, story, epic, idea, derivation gap,
doc-drift catch — with frontmatter-driven status on a kanban board.
## Heritage & philosophy: agile for the age of agents
The deck inherits three traditions deliberately:
- **XP story cards (Beck, 1999).** One card = one unit of work,
small enough to fit on an index card, with enough context that any
team member can pick it up. We keep the size discipline; the medium
is markdown instead of cardboard.
- **Scrum's Definition of Done (Sutherland & Schwaber).** Every card
carries a checkbox-list DoD as a closure contract. `goc done
<title>` refuses to flip the status until every box is `- [x]`. The
contract is machine-checkable, not a verbal handoff.
- **Kanban (Anderson, Toyota lineage).** Status mutates; position on
disk does NOT. A card stays at `deck/<title>/` for life — no moving
to `done/`, no archiving. Cross-references stay valid through every
state change.
The argument for keeping these now: original agile was a response to
**human handoff costs** — the 1990s problem of getting a feature from
analyst to developer to QA without losing intent. AI agents are the
most aggressive handoff-stress-test ever invented: dozens of
sub-agents, scheduled cron loops, and parallel /loop iterations all
read the same cards and mutate the same frontmatter. What was
"discipline" for human teams becomes **structurally lo