メニュー
Use when the user wants the integration contract for an ML or LLM service: API/tool methods, input/output schema, data contract rules, prompt hierarchy, retries, confidence routing, and fallback behavior.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants the rollout and ownership plan for an ML or LLM delivery: scope, workstreams, dependency map, rollout steps, blockers, readiness checklist, and transition notes.
Use when the user wants a quality and release-readiness plan for an ML or LLM service: dimensions, thresholds, datasets, review process, regression rules, and post-release quality review.
Use when the user wants the operational document for an ML or LLM service: ownership, alerts, common failures, incident response, degradation modes, recovery checks, and escalation contacts.
Use when the user wants to record one concrete architectural decision in an ML or LLM system, including alternatives, chosen option, rationale, risks, and impacted artifacts.
Use when the task is to create, update, sequence, or review the ML/LLM delivery document set as a pipeline rather than a single document. Covers PRD, system design, ADR, service spec, evaluation plan, delivery plan, runbook, security note, and prompt template.
Use when the user wants to review completeness, gaps, or consistency across the full ML/LLM document set, especially links between PRD, system design, ADR, service spec, evaluation, runbook, security, and prompt artifacts.
| name | ml-llm-service-spec |
| description | Use when the user wants the integration contract for an ML or LLM service: API/tool methods, input/output schema, data contract rules, prompt hierarchy, retries, confidence routing, and fallback behavior. |
Read:
../../../ML LLM Delivery Pipeline/04 Service Spec Template.mdUse this skill when another team or service must integrate with the ML/LLM component.