メニュー
Models stable business capabilities, levels, ownership, maturity and heatmaps. Use when mapping organisational abilities, decomposing strategy, or assigning capability ownership.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact.
Use when reviewing plans, recommendations, prioritisation, risk registers, retrospectives or agent outputs for judgement distortion from cognitive bias — not for checking whether an argument's premises validly support its conclusion.
Use when evaluating whether premises in plans, ADRs, reviews, security justifications or agent recommendations validly support their conclusions — for logical fallacies, not judgement distortion from cognitive bias.
Use when a coding agent needs robust problem solving, explicit decomposition, alternative-path exploration, program-aided reasoning, ReAct loops, or self-correction.
Use when generated code, plans, tests, prompts or architecture need critique, repair and verification before completion; especially for coding tasks requiring self-review, test-driven repair or quality gates.
Identifies risks, scores likelihood and impact, selects treatment, assigns owners and review cadence. Use when building or updating a risk register, treating agent autonomy risks, or deciding mitigate, transfer, accept or avoid.
| name | business-capability-modeling |
| description | Models stable business capabilities, levels, ownership, maturity and heatmaps. Use when mapping organisational abilities, decomposing strategy, or assigning capability ownership. |
| aliases | ["business-capability-modelling","capability-mapping"] |
Use when defining what a business must be able to do, not how work is performed.
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Align with BIZBOK business architecture practice: keep capabilities, value streams, processes, organisation, information concepts, initiatives and metrics separate, then link them from strategy to execution.
Do not mirror the organisation chart.
For a retail returns programme, model Manage Returns as the capability and decompose it into Authorise Return, Receive Returned Item, Assess Refund Eligibility and Recover Inventory Value. Do not name capabilities after systems such as Returns Portal; link the capability to the returns value stream, return request information concept, owner and heatmap criteria.
