メニュー
Answer questions about the project with file:line evidence from code and docs — read-only, never modifies files. Use when the user asks how or why something works, or weighs a "should we" question that needs an investigated answer rather than a change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run a PR's full review-fix cycle — wait for review and CI, fix failures, evaluate and reply to comments, then commit and push. Use whenever a PR was just opened or updated — the post-Ship phase of the Orchestrator loop.
Push the current branch and create a pull request with a title and description derived from the commit history. Use when the user asks to open a PR — the Ship step of the Orchestrator loop, always user-triggered.
Delegate a task's implementation wholesale to OpenAI Codex (`codex-run work`) — the whole requirements document in one long autonomous run — keeping policy, orchestration, and acceptance in the main loop. Use at the Implement step of the Orchestrator loop, for any multi-part build.
Cross-model second opinion from OpenAI Codex — `codex-run advise --context` reviews the current session, or pipe a brief. Triggers on "ask codex", "codex review", "second opinion", or the "Cross-model review" rules.
Define requirements before implementation — clarify constraints and design policy, then write a requirements spec and task breakdown for the Implementer to a gitignored plan file. Use at the Plan step of the Orchestrator loop, or whenever a request's scope needs pinning down before building. Never implements; the plan file is its only write.
Root-cause investigation — enumerate competing hypotheses, verify each with evidence, suggest a fix but never apply it. Use when an error, failing test, or anomaly needs diagnosing before any fix is written; implementation hands off to the Implementer.
| name | ask |
| description | Answer questions about the project with file:line evidence from code and docs — read-only, never modifies files. Use when the user asks how or why something works, or weighs a "should we" question that needs an investigated answer rather than a change. |
| argument-hint | [question] |
file:line for every finding.Explore for structure sweeps, reviewer for a lensed read, general-purpose for external sources) only when the surfaces are broad or independent.file:line evidence behind it, then what remains unknown or would sharpen the answer.For a deliberative question ("should we…", a trade-off rather than a lookup), also weigh the options through the 3–5 relevant lenses in $HOME/.claude/skills/decision-analysis/references/lens-catalog.md and present the trade-off each option accepts.