AI Agent Workflow Collection

Drive the local cliban kanban board via its CLI. Use when the user mentions cliban, kanban, ticket, issue, project, milestone, or asks you to capture/move work items, or asks what changed/what happened on the board.

The cliban workflow contract: per-repo adapter binding, status mapping, where work artifacts live vs the repo, and what a good plan contains. Loaded by workflow skills via requiresskills. CLI mechanics live in the cliban skill, not here.

Find the root cause of a bug on a cliban ticket and prove it, logging the hypothesis ledger to the ticket as you go. Use when asked to diagnose, debug, or investigate something broken, throwing, failing, or slow that already has a ticket. Ends at a proven cause; complete-issue writes the fix.

Explore a rough feature idea into a shared design, then land it on the cliban board as a ticket or an empty milestone. Use at the start of a new feature, before tickets exist — when the user wants to think something through, kick an idea around, or figure out what to build.

Grill a cliban ticket or milestone until every decision that changes the slicing is settled, then fill it with tracer-bullet tickets carrying native blocking edges. Use when the user wants a feature scoped, sliced, ticketed, grilled, or turned into a milestone — typically on the container explore-feature just created.

Bind a repo to its cliban board — project key, key-referencing policy, and branch/worktree convention. Run once per repo; re-run to change the binding.

Run the plugin's behavioral test scenarios (plugin-tests/scenarios/) against fresh subagents on hermetic throwaway boards, assert on resulting board state, and report a pass/fail table. Dev-only; use when asked to test, verify, or regression-check the plugin skills.