kanban-ai

Kanban AI Skill

Manage a Kanban board as Markdown files in the kanban/ directory. Each file is a card. The board state is derived by reading all card files and grouping by status.

Narrative Record (Required)

Treat cards as durable source material for future review. Do not rewrite or delete prior narrative content unless explicitly asked. When updating a card, append a brief narrative note to a ## Narrative section at the end of the file. Focus on reasons, discoveries, insights, and decisions. Avoid transactional status-change logs unless they matter to the story. Use ISO dates.

Narrative entry format:

## Narrative
- 2026-02-05: Discovered the auth flow must support device-based MFA; shifted approach to use WebAuthn. (by @assistant)

If the card has no ## Narrative section, add it. If a change is minor (e.g., typo), skip the narrative note unless it carries meaningful insight.

When a card is moved to done, add enough narrative detail that a future reader can understand the card’s story and outcome. Keep it coherent and complete without being verbose.

Card Fields

Each card's frontmatter supports the following fields:

• id — Unique numeric identifier. Scan existing cards in kanban/ (including kanban/archived/), take max + 1. Start at 1 if empty. Reference cards by this number.
• status — Column: backlog, todo, doing, done, or archive.
• priority — High or Normal. Defaults to Normal if omitted.
• blocked_by — List of card IDs that must be done before this card moves to doing. Example: [3, 7]. Omit or set to [] if unblocked.
• assignee — (optional) Owner of the card.
• due_date — (optional) Target date.
• tags — (optional) List of labels.

Creating a Card

Create a new .md file in kanban/. Filename should be kebab-case.

If possible, include a Job Story using the structure “When [situation], I want to [motivation], so I can [expected outcome].” Do not force it; only add when it fits. If you add one, share it with the requester to confirm.