board-author

Board Author

You create cards on a cboard. The worker drains and executes the board but is forbidden from inventing tasks — this skill is how new work gets onto the board.

Board root

Operate on a cboard board folder. Determine it in this order:

1. An explicit path the user gave.
2. The active board recorded by /cboard:init — <python> "${CLAUDE_PLUGIN_ROOT}/scripts/cboard_config.py" get. This is also board_cli.py's default when you omit --root.
3. The --root of a dashboard server that is currently running.
4. Otherwise tell the user to run /cboard:init first (or ask which folder).

How to create cards

Use the bundled CLI with the same Python interpreter the rest of the plugin uses (python3 / python / py -3 — whichever exists). It writes directly to the filesystem, so the dashboard does not need to be running; if it is, it picks the change up on its next poll.

<python> "${CLAUDE_PLUGIN_ROOT}/scripts/board_cli.py" --root "<board>" <command> …

Commands:

Goal	Command
New ticket	ticket "Title" [--project PID] [--body "markdown"]
New epic	epic "Title" [--project PID] [--body "markdown"]
Sub-ticket inside an epic	ticket "Title" --epic <epic-id> [--body "markdown"]
New project	project "Name" [--body "markdown"]
Move a card to a lane	move <id> <lane> (e.g. move 001-fix ready)
See what's on the board	list

Each create command prints a JSON line with the new id (and lane). Use list first when you need an existing epic id (for --epic) or project id (for --project).

Rules

• New top-level cards land in planning. The human decides what's ready to work, so a new card stays in Planning until they say otherwise. After creating one, offer to move it to ready ("want me to move it to Ready so the worker can pick it up?") and only run move <id> ready if they agree. Never silently auto-advance a card.
• Pick the right shape. A single self-contained task → a ticket. A larger effort that splits into several tickets → an epic with sub-tickets. A goal spanning multiple epics/tickets with shared docs → a project, then create its epics/tickets with --project.
• Write a useful body. Put the actual task description in --body (markdown) so the worker has something to act on — not just a title. For an epic, the body is the overall brief; each sub-ticket gets its own body.
• Don't reorder or delete existing cards, and don't move cards other than the just-created one to Ready on the user's say-so (above). Reordering and deletions are done in the dashboard.

After creating

Report what you made: ids, lane (planning), and for an epic the sub-tickets you added. If the user described a goal, summarize how you decomposed it (epic + N tickets, or M standalone tickets) so they can sanity-check the breakdown before moving anything to Ready.