メニュー
Derives business concepts and relationships from capabilities, value streams and processes. Use when linking business architecture artefacts to information concepts for data modelling.
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-information-concept-modeling |
| description | Derives business concepts and relationships from capabilities, value streams and processes. Use when linking business architecture artefacts to information concepts for data modelling. |
| aliases | ["business-information-concept-modelling","information-concept-modeling"] |
Use when translating business architecture into conceptual data, ontology or semantic models.
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 convert every noun into an entity.
From an onboarding value stream, extract concepts such as Customer, Application, Identity Evidence, Eligibility Decision and Account. Record synonyms like applicant/customer, define relationships such as customer submits application, and exclude implementation-only terms such as API payload or staging table. Hand the agreed concepts to conceptual data modelling with source traceability.
