メニュー
Classify a request before acting — intent, expected artifact, ambiguity, risk, persona class. Use when starting any new request and deciding whether to clarify, route, answer directly, or run a workflow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review code changes for correctness, error handling, scope creep, and style. Use when the goal mentions reviewing a PR, diff, or file.
Walk through a stack trace or error log to find the root cause. Use when the goal mentions debugging, investigating an error, or tracking down a bug.
Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes.
Outline unit tests for a function or module before writing them. Use when the goal mentions writing tests, test plan, or test coverage.
Keep effort proportional to risk — prefer the cheapest sufficient workflow, escalate only on evidence, refuse over-analysis on simple tasks. Use when choosing depth, level, or workflow shape.
Map required capabilities to persona roles and available skills. Detect missing skill coverage and decide whether to acquire a skill, request one, or proceed generically. Use when scoping a workflow.
| name | workflow-intake |
| description | Classify a request before acting — intent, expected artifact, ambiguity, risk, persona class. Use when starting any new request and deciding whether to clarify, route, answer directly, or run a workflow. |
The first move on any request is not to act — it is to classify. A wrong classification ten seconds in is cheaper than a wrong implementation ten minutes in.
A 4–6 line intake note: intent · artifact · ambiguity · risk · persona class · next move (clarify / route / answer / workflow). Then act on the next move.
