菜单
Initializes Agent Skills in a project by checking prerequisites and verifying the validator configuration. Use when the user says "init", "set up agent-skills", or "initialize agent-skills".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Creates a structured implementation task breakdown for a structured change, synthesizing proposal, design, and specs into self-contained per-task files. Use when the tasks artifact is the next step in a change.
How to ask users questions interactively: which tool to use, how to batch questions, and when to ask serially. Follow this skill when asking clarifying questions, requesting confirmation, collecting missing requirements, or pausing for user input. Invoked by other skills rather than directly by the user.
Creates design artifacts through collaborative brainstorming of approaches, architecture, and trade-offs. Use when the user says "design this", "create a design", "brainstorm approaches", or "write a design doc".
Adversarial review of a proposal — challenges the why, what, and how, and suggests alternative approaches. Use when the user says "review proposal", "challenge this proposal", "adversarial review", "poke holes", "stress test the proposal", or wants a second opinion on a proposal before moving to specs/design.
Evaluate whether a software idea is worth building, then write the proposal document. Use when the user wants to assess an idea, says "evaluate", "propose", "is this worth building", or "should we build". If the idea passes evaluation, write the proposal document using the provided template.
Reviews risky/notable assumptions and context gaps surfaced by implementor session reports, fixes high-confidence issues directly, and asks one clarifying question at a time for ambiguous findings. Use when the user says "review assumptions", "audit implementor assumptions", or when invoked by a workflow's assumption-review step.
| name | init |
| description | Initializes Agent Skills in a project by checking prerequisites and verifying the validator configuration. Use when the user says "init", "set up agent-skills", or "initialize agent-skills". |
Set up Agent Skills in the current project. This skill is idempotent — safe to re-run.
Announce at start: "Initializing Agent Skills in this project."
Check that the Agent Validator CLI is installed. If missing, tell the user what to install and stop.
agent-validator — run agent-validator --version.
npm install -g agent-validator, then run agent-validator init in your project, then re-run /codagent:init."npm install -g agent-validator@latest, then re-run /codagent:init."Use this shell snippet to compare versions:
version_gte() { [ "$(printf '%s\n' "$2" "$1" | sort -V | head -1)" = "$2" ]; }
Example: version_gte "$installed_version" "0.15" returns true if $installed_version ≥ 0.15.
If the CLI is missing or out of date, stop. The user must resolve it first, then resume /codagent:init.
Validator config (check after CLI passes):
.validator/config.yml must exist. If not found: "Validator config not found. Run agent-validator init in your project first, then re-run /codagent:init." Stop.Print a summary:
Agent Skills initialized successfully.
Available skills:
- /codagent:propose — evaluate an idea and write a proposal
- /codagent:spec — interview-driven requirement discovery
- /codagent:design — brainstorm architecture and write a design doc
- /codagent:plan-tasks — break a change into scoped task files
- /codagent:implement-and-validate — implement a single task and verify with the validator
- /codagent:finalize-pr — push PR, wait for CI, fix failures
Invoke /agent-validator:validator-commit skip to commit any scaffolding changes. Checks are skipped because init only writes boilerplate.
/codagent:init.validator/config.yml — only add/update entry points and reviews