メニュー
Use when AI-on-SaaS positioning must reflect a named vertical's use cases, regulator stance, evidence expectations, and risk language; use SaaS vertical positioning when AI-specific buyer concerns are absent.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when reviewing new or changed skills and bundled resources for unsafe installers, credential harvesting, hidden execution, or excessive permissions; use skill-writing for authoring structure.
Use when creating or normalising reusable proposal skills, trigger routes, contracts, references, or authoring automation; use skill-safety-audit instead for a read-only security review.
Use when routing, drafting, reviewing, or assembling a complete consulting proposal, EoI, bid, or tender response; use a numbered pipeline skill when only one known section is required.
Use when choosing whether an AI agent is included, sold as an add-on, or sold standalone; use the pricing skill for rate mechanics and the SLA skill for service commitments.
Use when selecting and adapting agent-specific contract exhibits for a proposal, MSA, or statement of work; use the addendum skill when drafting the full MSA/SLA overlay.
Use when defining intervention credits, abort rights, or refund mechanics for an agent engagement; use the SLA skill for broader credits and the outcome-pricing skill for success fees.
| name | ai-on-saas-vertical-positioning |
| description | Use when AI-on-SaaS positioning must reflect a named vertical's use cases, regulator stance, evidence expectations, and risk language; use SaaS vertical positioning when AI-specific buyer concerns are absent. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
saas-vertical-positioning).| Artefact or fact | Required? | Source/provider | If absent |
|---|---|---|---|
| The buyer's vertical and sub-vertical. | Required | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The regulator(s) and stance. | Required | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The candidate AI use cases. | Conditional | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The competitive set (named or inferred). | Conditional | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The buyer's hallucination tolerance and HITL appetite. | Conditional | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
vertical-ai-on-saas-<vertical>.md).ai-on-saas-win-themes-and-discriminators.md that fit the vertical.06-methodology.Stop condition: Stop before asserting scope, compliance, value, acceptance, or readiness when a load-bearing input is missing or contradicted.
Recovery: Record the gap, owner, and next evidence step; then return the narrowest qualified proposal content that remains supportable.
| Artefact | Consumer | Observable acceptance condition |
|---|---|---|
| Vertical positioning paragraph for Executive Summary. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Vertical-specific use-case list with hallucination tolerance per case. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Vertical discriminators block. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Vertical risk and regulator language. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
Vertical methodology variations for 06-methodology. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Vertical case studies or comparable-reference selection. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Evidence | Consumer | Acceptance condition |
|---|---|---|
| Input-and-assumption record | Proposal lead and reviewer | Every load-bearing claim maps to a source, approved assumption, or explicit gap. |
| Decision and review record | Buyer owner and delivery lead | The selected option, rationale, owner, stop condition, and approval status are visible. |
| Section acceptance check | Evaluator-readiness reviewer | Each output meets its stated acceptance condition and unresolved checks are not presented as passed. |
This skill may read supplied tender, discovery, architecture, commercial, security, and operating evidence and draft proposal artefacts within the authorised workspace. It must not publish, send, certify compliance, accept contractual terms, change production systems, spend funds, or disclose confidential evidence without explicit authority. Review and analysis remain read-only by default.
If files, current legal or technical evidence, calculation tools, network access, or reviewers are unavailable, produce the narrowest useful qualified draft. Label assumptions and checks as not assessed, omit unsupported assurances or figures, and state the exact evidence and owner needed to complete the work. An unavailable check never becomes a pass.
| Choice | Action | Failure or risk avoided |
|---|---|---|
| Jurisdiction or sector rule | Verify the named requirement and qualify applicability before citing it | Generic or legally inaccurate positioning |
| Missing load-bearing evidence | Stop the affected claim, record the gap and owner, and continue only with separable supported content. | Fabricated assurance or hidden dependency |
| Conflicting buyer and supplier evidence | Surface the conflict for decision; do not silently choose the favourable version. | Misaligned scope, price, or acceptance |
| Irreversible, contractual, publishing, or production action | Obtain explicit authority and preserve an approval record before acting. | Unauthorised commitment or mutation |
For an insurer, connect the AI use case to the claims workflow, governed data, review authority, customer-harm controls, and regulator expectations; do not rely on generic industry language.