Menu
Edit or remove existing agents — rename, adjust budget, retire
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-agent-edit |
| description | Edit or remove existing agents — rename, adjust budget, retire |
| kandev | {"system":true,"version":"0.42.0","default_for_roles":["ceo"]} |
You can edit an existing agent's settings or remove an agent that's no longer needed.
$KANDEV_CLI kandev agents update --id A-1 --name "Senior Reviewer"
$KANDEV_CLI kandev agents update --id A-1 --budget-monthly-cents 5000
Pass 0 to mean "unlimited" (subject to workspace policy). Pass -1 and the flag is ignored (allows scripted updates with optional fields).
$KANDEV_CLI kandev agents update --id A-1 --max-concurrent-sessions 1
$KANDEV_CLI kandev agents delete --id A-1
The backend rejects deletes for agents that are currently working. Use kandev agents list to confirm status: idle first.
role after create — re-hire).--budget-monthly-cents.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.