with one click
kandev-task-comment
Post a comment on any task as the current agent
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.
Menu
Post a comment on any task as the current agent
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
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.
| name | kandev-task-comment |
| description | Post a comment on any task as the current agent |
| kandev | {"system":true,"version":"0.42.0","default_for_roles":["ceo","worker","specialist","assistant","reviewer"]} |
You can drop a comment on any task without creating a new one. Use this when:
$KANDEV_TASK_ID is auto-filled when omitted:
$KANDEV_CLI kandev tasks message --prompt "Got it — starting now."
$KANDEV_CLI kandev tasks message --id T-42 --prompt "Blocked: the worktree has a dirty submodule. Owner: please investigate."
comment addagentctl kandev comment add writes as the user. tasks message writes as the agent (you). Most office work flows through agent comments — only use comment add when you're acting as a test fixture or impersonating user input.
"Done." on every heartbeat — only when you actually made progress.ask_user_question (still an MCP tool, available in office mode).