kandev-task-ops

$npx mdskill add kdlbs/kandev/kandev-task-ops

Operates Office tasks like listing, reading conversations, and posting comments.

  • Lists workspace tasks and reads task conversations for coordination.
  • Depends on references/tasks.md and references/comments.md for data.
  • Chooses comments over subtasks for small updates and avoids decision questions.
  • Delivers results by reading or writing to task files and using task update commands.

SKILL.md

.github/skills/kandev-task-opsView on GitHub ↗
---
name: kandev-task-ops
description: Operate Office tasks when you need to list workspace tasks, read a conversation, or post an agent-authored comment.
kandev:
  system: true
  version: "0.42.0"
  default_for_roles: [ceo, worker, specialist, assistant, reviewer]
---

# Task Ops

Use this skill for task communication and task-level operations outside the singular task status flow in `kandev-protocol`.

## Choose the operation

- List tasks or read task conversations: read `references/tasks.md`.
- Post an agent-authored comment to your current task or another task: read `references/comments.md`.

## Rules

- Prefer comments over spawning subtasks for small coordination updates.
- Keep comments concise and specific.
- Use `kandev task update --status <status>` for signed status changes. Workflow-step moves and archival require a human or admin action.
- Do not ask the human a decision question via task comment; use the available user-question tool or `kandev-escalation`.

More from kdlbs/kandev

SkillDescription
acp-debugDebug an ACP agent CLI by spawning it, speaking raw JSON-RPC, and capturing every frame to a JSONL file. Use when the user asks to probe an agent's capabilities, compare agents, test a prompt against an agent, inspect raw ACP wire frames, or investigate why an agent fails to initialize.
add-integrationAdd a new third-party integration (Jira/Linear-style) — per-workspace credentials, 90s auth-health poller, settings page, link/import buttons. Use when scaffolding a new external service integration.
clean-branchesDelete local branches whose remote has been deleted ([gone]), including their worktrees. Use for branch cleanup after merging PRs.
create-kandev-pluginCreate, modify, debug, test, package, or publish a Kandev runtime plugin in its dedicated repository. Use only when the requested work targets a Kandev plugin implementation or its release and marketplace lifecycle, including fixing a bug in an existing plugin. Do not use for agent skills, MCP servers, general integrations, or Kandev host, SDK, loader, and registry changes that do not also change a plugin.
docs-maintainerKeep public Kandev docs current when code or behavior changes affect CLI commands, config keys, install/deploy flows, workflows, executors, APIs, screenshots, or user-facing terminology. Use this before finishing any change with public documentation impact, and when reviewing whether a change needs docs.
harness-improvementImprove Kandev's AI harness from session learnings or explicit requests. Use when the user asks to record learnings, update or create skills, agents, subagents, commands, AGENTS.md/CLAUDE.md guidance, or adapt harness files across Claude, Codex, Cursor, or OpenCode.
kandev-approvalsClear the CEO approval queue when hire requests, budget grants, or other sensitive Office mutations are waiting for approve or reject decisions.
kandev-config-syncSynchronize Office workspace configuration with the .kandev folder when exporting reviewable config, importing committed config, seeding a workspace, or reviewing a config diff.
kandev-escalationEscalate to a human when required information, access, credentials, or a product decision blocks completion and no reasonable default is available.
kandev-projectsList and create Office projects, then place new tasks in the correct project when organizing workspace work by repository.