Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Kanban Workflow is a TypeScript skill for a stage-based agentic co-worker that integrates PM platforms via CLI-auth adapters only (no direct HTTP auth). It p...
Kanban Workflow is a TypeScript skill for a stage-based agentic co-worker that integrates PM platforms via CLI-auth adapters only (no direct HTTP auth). It p...
This item is timing out or returning errors right now. Review the source page and try again later.
Use the source page and any available docs to guide the install because the item is currently unstable or timing out.
I tried to install a skill package from Yavira, but the item is currently unstable or timing out. Inspect the source page and any extracted docs, then tell me what you can confirm and any manual steps still required. Then review README.md for any prerequisites, environment setup, or post-install checks.
I tried to upgrade a skill package from Yavira, but the item is currently unstable or timing out. Compare the source page and any extracted docs with my current installation, then summarize what changed and what manual follow-up I still need. Then review README.md for any prerequisites, environment setup, or post-install checks.
Provide a reusable core for a project-management βco-workerβ that: Uses the existing stage:* lifecycle as the canonical state machine. Integrates with PM platforms via CLI-managed auth only (no direct HTTP auth handling). Centralizes workflow/rules/runbooks so GitHub/Planka/Plane/Linear implementations share logic.
Treat these labels/states as canonical (and the only stages the agent should consider): stage:backlog stage:blocked stage:in-progress stage:in-review Notes: Done/closed is platform-specific and intentionally not part of the canonical stage set. Adapters map platform concepts (labels, lists, statuses, custom fields) into this canonical set.
Canonical entities: WorkItem, Project, Comment, Stage. Canonical events: WorkItemCreated, WorkItemUpdated, StageChanged, CommentAdded, etc. Workflow engine: stage-based worker loop + clarification/comment templates. State: cursors + dedupe + snapshots for diffing.
Adapters are βsmart wrappersβ that: Call existing CLIs (e.g. gh, planka-cli, plane-cli, linear-cli), relying on their auth/session. Compose multiple CLI calls to implement higher-level operations. Synthesize events by polling + snapshot diffing when webhooks or event types are missing. Canonical adapter entrypoints live in src/adapters/: github.ts (gh CLI) planka.ts (planka-cli) plane.ts (plane-cli; Api2Cli workspace) linear.ts (linear-cli; Api2Cli workspace) See also: src/adapters/README.md for CLI links and assumptions.
Library entry points: tick() (poll β normalize β diff β events) verb-level workflow helpers: show, next, start, update, ask, complete, create automations: runProgressAutoUpdates() CLI entry point: src/cli.ts (provides kanban-workflow <verb>; see README for setup flags)
All kanban-workflow <verb> commands print a What next: tip after execution to guide the canonical flow: setup β next β start β (ask | update) β complete β next After start, the tip additionally reminds you to run the actual execution/implementation work in a subagent, then report back via ask/update. If config/kanban-workflow.json is missing or invalid, all commands error and instruct you to complete setup.
Setup writes config/kanban-workflow.json and validates that the selected platform CLI is installed + authenticated. Required: kanban-workflow setup --adapter <github|plane|linear|planka> ... stage mapping flags: --map-backlog, --map-blocked, --map-in-progress, --map-in-review Adapter flags (summary): GitHub: --github-repo <owner/repo>, optional --github-project-number <number> Plane: --plane-workspace-slug <slug>, --plane-project-id <uuid>, optional --plane-order-field <field> Linear: --linear-team-id <id> or --linear-project-id <id>, optional --linear-view-id <id> Planka: --planka-board-id <id>, --planka-backlog-list-id <id>
While a task is in stage:in-progress, Kanban Workflow can post an automatic progress update comment every 5 minutes. Use runProgressAutoUpdates() and persist its state in your agent/runtime.
scripts/: deterministic helper scripts used by adapters or the core. references/: schemas and adapter notes (loaded on demand). assets/: runbooks/SOP templates.
The current core implementation is in TypeScript under src/.
Extend the adapter port to include idempotent write operations (comment/transition/label) in addition to fetchSnapshot(). Finish and validate the Plane + Linear adapters (consume plane-cli / linear-cli output schemas). Decide on the authoritative mapping rule for stage β platform state (names vs explicit mapping table) and codify it. Add a small CLI surface for Kanban Workflow itself (e.g. kanban-workflow tick --adapter plane --workspace ... --project ...).
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.