Menu
List, move, archive, and message tasks via agentctl
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | kandev-tasks |
| description | List, move, archive, and message tasks via agentctl |
| kandev | {"system":true,"version":"0.42.0","default_for_roles":["ceo","worker","specialist"]} |
The singular agentctl kandev task group handles a single task (the one you're working on). This plural group handles tasks across the workspace.
# Everything
$KANDEV_CLI kandev tasks list
# Filtered
$KANDEV_CLI kandev tasks list --status todo
$KANDEV_CLI kandev tasks list --assignee A-1
$KANDEV_CLI kandev tasks list --project P-12
$KANDEV_CLI kandev tasks move --id T-1 --step ws-review
$KANDEV_CLI kandev tasks move --id T-1 --step ws-review --prompt "Please review this PR; gating on QA."
The optional --prompt is queued as the first comment the destination step sees — use it for handoff context.
$KANDEV_CLI kandev tasks archive --id T-1
Idempotent: archiving an already-archived task is a no-op.
$KANDEV_CLI kandev tasks message --id T-1 --prompt "Heads up: design changed, see comment #42."
The message lands as an agent comment on the task. The assignee's next heartbeat will see it.
$KANDEV_CLI kandev tasks conversation --id T-1
Use sparingly — comments can be long. Prefer the inline batch on comment-driven wakes.
Kandev release & versioning conventions — single SemVer across npm, Homebrew, GitHub release. Use when cutting a release, debugging release artifacts, or answering questions about version channels.
Review changed code for quality, security, and architecture compliance. Use after implementing features or before opening PRs.
Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix or /tdd for code changes.
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.
Ensures UI feature work ships with desktop and mobile parity, responsive behavior, and mobile Playwright E2E coverage. Use when implementing, planning, reviewing, or testing any new feature, page, component, workflow, form, dialog, sidebar, navigation, dashboard, or visual UI change; if work touches frontend or user-facing UI, this skill must run even when user mentions only desktop or says "new feature".
Create a committed implementation plan from a feature spec. Explores the codebase, designs the approach, and produces docs/plans/<feature>/plan.md plus individual task files. Use after writing a spec and before implementing.