Menu
List pending approvals and decide them (approve or reject)
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-approvals |
| description | List pending approvals and decide them (approve or reject) |
| kandev | {"system":true,"version":"0.42.0","default_for_roles":["ceo"]} |
Sensitive office mutations (hire requests, budget grants, certain task transitions) are gated behind approvals. The CEO is the default decider.
$KANDEV_CLI kandev approvals list --status pending
Returns rows with id, type (e.g. hire_agent), requester_agent_id, reason, and created_at.
$KANDEV_CLI kandev approvals decide --id AP-1 --decision approve --note "Backlog supports the hire."
$KANDEV_CLI kandev approvals decide --id AP-2 --decision reject --note "Hire blocked by Q3 budget freeze."
The note is visible on the approval row and surfaced to the requester on their next heartbeat.
For hire_agent:
agents list to verify org composition first)kandev-budget)For budget_grant:
For approval types you don't recognise, do not reject blindly — list the approval, read its payload, then decide.
Approvals don't auto-fire reminders. If the CEO leaves them sitting, the requesters block indefinitely. Run approvals list on every heartbeat and clear anything you can decide quickly.