kandev-projects

$npx mdskill add kdlbs/kandev/kandev-projects

List and create Office projects, then place tasks in the correct project.

  • Solves organizing workspace work by repository into projects.
  • Depends on the kandev CLI for project and task management.
  • Uses repository URLs or paths to assign tasks to existing projects.
  • Returns project IDs for use in subsequent task creation commands.

SKILL.md

.github/skills/kandev-projectsView on GitHub ↗
---
name: kandev-projects
description: List and create Office projects, then place new tasks in the correct project when organizing workspace work by repository.
kandev:
  system: true
  version: "0.42.0"
  default_for_roles: [ceo]
---

# Projects

Use project IDs returned by the CLI. Project access is scoped to the current
Office workspace, and project creation is permission checked.

## Inspect projects

```bash
$KANDEV_CLI kandev projects list
```

## Create a project

`--name` is required. Repeat `--repository` for each repository URL or local
path the project owns.

```bash
$KANDEV_CLI kandev projects create \
  --name "Payments" \
  --description "Payment services and checkout" \
  --repository "https://github.com/acme/payments" \
  --repository "/workspace/checkout"
```

Optional project fields are `--lead-agent-profile-id`, `--color`,
`--budget-cents`, and `--executor-config`.

## Create work in a project

Pass the returned project ID when creating a task:

```bash
$KANDEV_CLI kandev task create \
  --title "Add payment retry policy" \
  --project "$PROJECT_ID" \
  --assignee "$AGENT_ID"
```

Do not create a duplicate project when an existing project already owns the
repository. Office runs do not administer workspaces.

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-protocolFollow the core Office agent protocol on wakeup, including parsing KANDEV_* context, checking blockers, commenting progress, updating status, and using the CLI safely.