Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Developer Tools
Kanban Workflow
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...
skill openclawclawhub Free
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...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, _meta.json, package-lock.json, package.json, references/ARCH_REVIEW.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.12
Provenance
- Publisher
- simonvanlaak
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Goal
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.
Canonical stage model
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.
Core (platform-agnostic)
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 (platform-specific)
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.
Entry points
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)
CLI ergonomics: "What next" tips
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 (flags-only)
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>
Continuous status updates
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.
Recommended repo layout
scripts/: deterministic helper scripts used by adapters or the core. references/: schemas and adapter notes (loaded on demand). assets/: runbooks/SOP templates.
Repo status
The current core implementation is in TypeScript under src/.
Next implementation steps
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 ...).
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs3 Config
- SKILL.md
- README.md
- references/ARCH_REVIEW.md
- _meta.json
- package-lock.json
- package.json