一键导入
kandev-hiring
Hire new agents via agentctl, gated by the workspace approval policy
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Hire new agents via agentctl, gated by the workspace approval policy
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
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-hiring |
| description | Hire new agents via agentctl, gated by the workspace approval policy |
| kandev | {"system":true,"version":"0.42.0","default_for_roles":["ceo"]} |
You can hire new agents to expand capacity. Hiring is gated by the workspace's approval policy: in most workspaces a new agent enters pending_approval status and only becomes idle after a human approves the hire_agent request.
Before calling the API, decide:
Reviewer, Frontend-Worker)worker, specialist, assistant, reviewer (CEOs hire each of these; you do not hire other CEOs)$KANDEV_CLI kandev agents create \
--name "Frontend-Worker" \
--role worker \
--reason "Three frontend tasks queued and the existing worker is at capacity"
The response includes the new agent's id and status. If status: pending_approval, the agent is queued — do not assign work to it until it flips to idle.
$KANDEV_CLI kandev approvals list --status pending
Or just re-list the team and look at the new agent's status:
$KANDEV_CLI kandev agents list
agentctl kandev tasks message to ask an existing agent.kandev-budget).Hiring without a clear reason will be rejected at the approval step.