Clear the CEO approval queue when hire requests, budget grants, or other sensitive Office mutations are waiting for approve or reject decisions.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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-team-admin)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.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Debug 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 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.
日本語の概要は準備中です。原文の説明を表示しています。
Delete local branches whose remote has been deleted ([gone]), including their worktrees. Use for branch cleanup after merging PRs.
日本語の概要は準備中です。原文の説明を表示しています。
Review changed code for quality, security, and architecture compliance. Use only when the user explicitly requests local review or a PR finding requires it.
日本語の概要は準備中です。原文の説明を表示しています。
Stage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says "commit", or before pushing a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Curate the right project context before coding or debugging. Use when starting a new session, switching areas of the codebase, output quality is drifting, a task spans backend/frontend/docs, or external instructions need to be reconciled with Kandev conventions.
日本語の概要は準備中です。原文の説明を表示しています。