mission-kanban

Decomposes multi-part mission objectives into kanban tasks and routes the next sub-skill.

Updated May 22, 2026
One-click install
npx skills add https://github.com/MathieuDoyon/mission --skill mission-kanban
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-kanban
Source: https://github.com/MathieuDoyon/mission/tree/main/.claude/skills/mission-kanban
Command: npx skills add https://github.com/MathieuDoyon/mission --skill mission-kanban

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mission objectives often split into multiple independent slices, and advancing them in the wrong order creates delays, conflicts, and unclear progress.

Core Features & Use Cases

  • Kanban decomposition and task shaping: Turns a clarified multi-part parent objective into 3–8 outcome-based tasks that are independent enough for parallel work.
  • Next-task selection with dependency-aware scoring: Chooses which slice to advance next using rules that prioritize unblocking, risk reduction, and finishing in-flight work.
  • Per-task isolation strategy: Decides whether task work should stay in the shared tree or run in an isolated worktree to avoid collisions.
  • Deferred merge to the review judge: When tasks finish, routes reconciliation to mission-review rather than attempting cross-task merges inside kanban.

Quick Start

Use mission-kanban to decompose a multi-part objective into kanban tasks, pick the best next slice, and delegate mission sub-skills toward that slice while keeping task isolation consistent.

Frequently Asked Questions about mission-kanban

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

FAQPage Schema
How do I decompose a multi-part mission into parallel kanban tasks?

Kanban decomposition breaks a multi-part parent objective into 3–8 independent, outcome-based tasks. This allows parallel work by ensuring each slice is isolated enough to advance without creating conflicts or delays across the broader mission.

When do I need kanban task routing for mission planning?

Kanban task routing is needed when a mission plan contains three or more reorderable steps. It selects the highest-value slice to advance next by applying dependency-aware scoring rules that prioritize unblocking, risk reduction, and finishing in-flight work.

How do I choose between shared tree and worktree isolation for kanban tasks?

Worktree isolation prevents collisions when advancing independent kanban slices in parallel, while shared tree work suits tasks with overlapping dependencies. The routing mechanism evaluates task independence to decide the correct isolation strategy.

How does kanban task state reconcile when parallel slices finish?

When parallel kanban slices finish, the routing mechanism defers cross-task reconciliation to the review judge. It delegates final merge decisions rather than attempting cross-task merges directly inside the kanban workflow.

Can I use kanban task routing for mission plans with fewer than three steps?

Kanban task routing applies to mission plans containing three or more reorderable steps. For smaller objectives, the dependency-aware scoring and worktree isolation strategies provide no meaningful parallel tracking advantage.

Why does task decomposition prioritize unblocking and risk reduction?

Task decomposition prioritizes unblocking and risk reduction to advance the highest-value slice first. This dependency-aware scoring ensures that in-flight work finishes efficiently and prevents delays caused by routing the wrong mission sub-skill.