菜单
Use when designing, changing, or reviewing Takode CLI commands, JSON output schemas, inspection commands, or orchestration command output that may expose session objects, prompts, histories, logs, recordings, images, tool results, artifacts, or other bulky/uncommon fields.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | takode-cli-design |
| description | Use when designing, changing, or reviewing Takode CLI commands, JSON output schemas, inspection commands, or orchestration command output that may expose session objects, prompts, histories, logs, recordings, images, tool results, artifacts, or other bulky/uncommon fields. |
Use this skill before changing Takode CLI behavior or output shape.
Default output is compact, operational, and enough for the next decision. Bulky, uncommon, debug, or raw fields require explicit reveal through a flag, field name, range, or detail command.
--details, --include <field>, or a narrowly named detail command.detail <id>, --full, --verbose, --details, --include <field>, --limit, --count, or --from for deeper inspection.Do not make every row or message more verbose to support an occasional follow-up workflow. When a detail is only needed for navigation, debugging, or rare disambiguation, prefer an explicit lookup or reveal path over adding that detail to default rows.
Examples:
takode peek <session> --turn-containing <msg-id> over printing a turn id on every takode grep result.threads: line in scan/peek over default verbose per-thread status summaries.read, JSON, --details, --include, or a targeted command when they are not needed for the common scanning task.Before adding a default field to repeated rows, ask:
If the field mainly supports a rare follow-up, do not include it by default. Add or improve the follow-up command instead.
Do not include these by default:
If a bulky field is useful, expose it by name and document the reveal path in help text.
injectedSystemPrompt, to prove default output omits it.Leader instructions should prefer compact plain output for judgment calls and routine dispatch. Use --json only for programmatic decisions, and use compact JSON before reaching for --details or --include.
Dispatch workflow for leader/orchestrator sessions. Use when dispatching a quest to a worker, choosing which worker to assign, spawning new worker sessions, or deciding whether to reuse vs spawn. Triggers: 'dispatch', 'send quest', 'assign worker', 'spawn worker', 'which worker', 'reuse or spawn'.
Cross-session orchestration for Takode. Use when you need to interact with other sessions: listing active sessions, peeking at session activity, reading messages, sending instructions to workers, or spawning new sessions. Triggers: 'check on workers', 'send to session', 'orchestrate', 'coordinate agents', 'list sessions', 'peek at session', 'what are my sessions doing', 'check session status'.
Confirm quest intent before creating a new quest or refining an idea into a worker-ready quest. Invoke when a user asks to create, file, refine, scope, or prepare a quest, or before materially rewriting quest title/description/tags as part of refinement. Do not use for routine quest feedback, claiming, completion, verification checks, or other bookkeeping.
Port changes from a git worktree to the main repository. This is the skill behind `/port-changes`; `worktree-rules` remains the underlying skill slug/directory. Use when asked to 'port changes', 'sync to main', 'push to main repo', '/port-changes', or when porting worktree commits.
Quality review for another agent's change. Invoke it with a concise description of the change to review, then inspect that worker's status and diff and later verify whether required findings were addressed.
Adversarial review of a worker's completed task. Independently evaluates whether the worker did thorough, honest work or took shortcuts. Returns ACCEPT or CHALLENGE with specific questions. Invoked by the reviewer session after being spawned by the leader.