card-write

Route open loops to GitHub issues or a kanban.md board in a one-line card format.

1|Updated Nov 21, 2015
One-click install
npx skills add https://github.com/mark-brannan/dotfiles --skill card-write-mark-brannan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: card-write
Source: https://github.com/mark-brannan/dotfiles/tree/main/.claude/skills/card-write
Command: npx skills add https://github.com/mark-brannan/dotfiles --skill card-write-mark-brannan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent or user finds an open loop mid-session — a question, a check, a piece of work — it needs exactly one home, captured immediately with its link and context, instead of being lost or duplicated across trackers. ## Core Features & Use Cases - Routing rules: Decides where each loop lives — work state stays on the PR or issue, questions pass a one-way-door test, checks run immediately, and only agent-startable work becomes a GitHub issue. - Kanban card format: Writes one-line imperative cards with a mandatory link to the global kanban.md board, with required fields for ruling cards (default, undo, until, risk) and click-work cards (why you, why this). - Lint enforcement: A kanban-lint.sh check rejects ticked boxes, missing links, state words, and cards that duplicate PR or issue state. - Use Case: During a code review an agent finds a decision that has no safe default; it writes a ruling card under ## Needs ruling with its evaluation so the human can answer in one word. ## Quick Start Ask the agent to capture a finding by saying "card that" or "add a card to the board" and it will route the loop to the right home and write the line.

Frequently Asked Questions about card-write

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

FAQPage Schema
How do I capture an open loop found during an agent session?▼

Say "card that" or "add a card" and the loop is routed to its one home: work state stays on the PR or issue, agent-startable work becomes a labelled GitHub issue, and everything else becomes a one-line card on the kanban.md board.

When should a finding become a GitHub issue instead of a kanban card?▼

File an issue only when a fresh session could start from the body alone, with a link to the evidence and a next action an agent can execute. Below that bar the finding becomes a board card, a log line, or nothing.

What format does a kanban card follow?▼

Each card is one line with a short name, an imperative action, and a mandatory link. Ruling cards add default, undo, until, and risk fields; click-work cards add why you and why this proofs.

Why does the kanban lint reject my card edit?▼

The lint rejects ticked boxes, cards without links, state words like merged or awaiting, review-or-merge verbs pointing at PRs, and ruling or click-work cards missing their required fields.

What happens to cards when the work is done?▼

Completed cards are deleted, never ticked, since the board is a work-in-progress list and git history keeps the record. Answered ruling cards move to a decisions.md file before removal.