メニュー
Use to assess whether current documentation through an MCP, docs, or search integration may help with a dependency that may be newer than the client's knowledge.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.
Use after a grill-change session is complete to turn the agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs.
Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.
Use after a grill-change session is complete to turn the agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs.
Use to run a bounded security-review, patch, and retest loop that stops on green, on no diff, or on a repeated identical finding.
Use before handing off an implementation to compare the diff against the spec, tests, docs, contracts, and safety rules.
| name | mcp-fit-check |
| description | Use to assess whether current documentation through an MCP, docs, or search integration may help with a dependency that may be newer than the client's knowledge. |
Report the dependency, why current docs may help, the recommended integration category, its risk, and the explicit next decision for the user.
