Domain Capability Portfolio Architect

    1

    Architects business capability portfolios: 3-tier capability hierarchies, maturity heatmaps, and context mapping.

    $9

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    Domain Capability Portfolio Architect

    Example session with this skill installed

    Architect enterprise domain business capability taxonomy and investment portfolio for our Banking Suite.

    • Subject: banking-cap-arch-001 mapping capabilities across 180 microservices and 4 core banking divisions.
    • Deciders: Chief Enterprise Architect (David O'Reilly) and Head of Capability Governance (Elena Rostova).
    • Scope: Structuring 3-tier capability taxonomy (Level 1 Domain, Level 2 Core, Level 3 Operational) and maturity heatmaps.
    • Tension: Product teams built 3 duplicate KYC identity services independently; David O'Reilly and Elena Rostova strictly reject redundant capability builds, citing incident INC-4922 where duplicate KYC tools cost $1.8M in wasted licenses. They mandate an authoritative capability map: single-owner capability assignment, mandatory reuse intake, and zero orphan microservices.

    Write the domain capability architecture overview under docs/.

    • Read your context and instructions
    • Compiled the domain capability portfolio
    • Generated the document

    Wrote docs/architecture/domain-capability-architect/00-overview/domain-capability-architect-overview.md and docs/architecture/domain-capability-architect/verification/fitness-self-check.md. Complete enterprise domain capability architecture specification establishing capability taxonomy hierarchies, maturity heatmaps, capability-to-context mappings, and investment roadmaps.

    skill: domain-capability-architect

    Domain Capability Architecture: Enterprise Banking Suite [CAPARCH-FIN-001]

    Summary

    This specification establishes the enterprise domain capability architecture, capability taxonomy hierarchy, and investment governance framework for the Enterprise Banking Suite under run ID banking-cap-arch-001. It maps business capabilities across 180 microservices and 4 core banking divisions (Payments, Lending, Wealth, Compliance). It decisively eliminates the capability duplication, redundant SaaS licensing, and ownership ambiguity demonstrated in incident INC-4922 (where three separate product squads independently built conflicting customer KYC identity verification services, incurring $1.8M in redundant vendor fees and failing AML regulatory audits). The architecture establishes a formal

    3-tier capability taxonomy hierarchy (Level 1 Domain, Level 2 Core Capability, Level 3 Operational Capability), maps capabilities 1:1 to authoritative bounded contexts, provides capability maturity heatmaps, and enforces capability reuse governance.

    Detailed Description

    In large enterprise organizations, product squads organized around short-term feature deliveries frequently build overlapping technical solutions to identical business problems. Without an authoritative capability map, business leaders cannot identify redundant investments, understand system capability gaps, or determine which team owns the definitive system of record for a capability like "Identity Verification" or "Credit Risk Assessment." Domain capability architecture decouples what the business does (capabilities) from how software is currently implemented, creating a stable strategic lens for enterprise portfolio planning.

    Enterprise Business Capability Hierarchy: Banking Suite
                           │
        ┌──────────────────┼──────────────────┐
        ▼                  ▼                  ▼
[ Capability Level 1: ]   [ Capability Level 1: ]   [ Capability Level 1: ]
  Payments & Clearing       Credit & Lending          Wealth & Custody
        │                  │                  │
        ▼                  ▼                  ▼
[ Capability Level 2: ]   [ Capability Level 2: ]   [ Capability Level 2: ]
  Settlement Execution      Loan Underwriting         Portfolio Rebalancing
        │                  │                  │
        ▼                  ▼                  ▼
[ Capability Level 3: ]   [ Capability Level 3: ]   [ Capability Level 3: ]
  Instant ACH Clear         Covenant Audit            Tax-Loss Harvesting
        │                  │                  │
        └──────────────────┼──────────────────┘
                           ▼ (Shared Enterprise Cross-Cutting Capability)
                 [ Identity & KYC Verification ]
                   (Single Authoritative Owner: Compliance Squad)

    Criteria and weights

    CriterionWhy it matters hereWeightSource of the weight
    Elimination of Duplicate Capability BuildRedundant services create massive technical debt and multi-million-dollar vendor waste (INC-4922).0.40David O'Reilly (Chief Enterprise Architect)
    Single System of Record AuthorityEach business capability must have exactly one authoritative owning team and bounded context.0.30Elena Rostova (Head of Capability Gov)
    Capability-to-Service TraceabilityEnterprise capability taxonomy must map directly to deployable microservice artifacts.0.15Core Banking Engineering SLA
    Investment & Modernization Heatmap ClarityBusiness leaders require clear visibility into capability maturity to direct quarterly budget.0.15Executive Strategy Committee

    Alternatives rejected

    OptionWhy it was not takenUnder what evidence it would win
    Ad-Hoc Squad-Led Capability CreationCaused INC-4922 $1.8M vendor waste; 3 teams built identical KYC services independently.Early-stage exploratory startups where product-market fit is completely unknown.
    Vendor Capability Matrix Only (Gartner / TOGAF generic)Generic models lack specific banking ledger and regulatory compliance realities.Organizations outsourcing 100% of IT operations to turnkey commercial SaaS vendors.
    Domain Capability Architecture (Chosen)Retains selection; establishes clear capability boundaries, eliminates duplication, and aligns investment.Multi-division financial institutions modernizing core banking platforms.

    Contracts and Invariants

    Single Authoritative Capability Ownership [INV-CAPARCH-01]
  Each Level 3 business capability must map to exactly one authoritative bounded context and owning squad.
  Deploying duplicative implementations of an existing certified enterprise capability is prohibited.

Mandatory Capability Registry Intake [INV-CAPARCH-02]
  New product initiatives requiring capabilities must check the enterprise capability registry.
  Teams must reuse existing capability APIs before requesting capital budget to build new solutions.

Zero Orphan Microservice Policy [INV-CAPARCH-03]
  Every production microservice repository must declare its supporting capability ID in its architecture metadata.
  Deploying un-mapped or un-categorized backend services is blocked by CI governance gates.

    Ownership and Handoffs

    ConcernOwnerHandoff payloadBlocked until
    Enterprise Capability Map & TaxonomyChief Enterprise Architect (David O'Reilly)enterprise_capability_map_specExecutive Committee sign-off
    Capability Maturity Scoring & GovernanceHead of Capability Gov (Elena Rostova)capability_maturity_heatmapBusiness unit review
    Service Metadata & Capability BindingPlatform Engineering Leadservice_catalog_capability_metadataDeveloper portal release
    Capital Budget Allocation AlignmentFinOps & Portfolio Planningit_investment_capability_alignmentAnnual budget cycle

    Traceability

    ClaimClassificationSourceFreshness
    180 microservices across 4 banking divisionsprovidedEnterprise scope intakeCurrent
    Incident INC-4922 $1.8M duplicate KYC wasteprovidedForensic audit recordHistorical
    3-tier capability taxonomy standarddecidedDavid O'Reilly & Elena Rostova2026-09-15
    Single authoritative capability ownershipdecidedArchitectural invariant INV-CAPARCH-012026-09-15
    Mandatory capability reuse intakedecidedArchitectural invariant INV-CAPARCH-022026-09-15
    Zero orphan microservice policydecidedArchitectural invariant INV-CAPARCH-032026-09-15

    Verification

    No validator was supplied, so no command was run.

    Reviewer self-check against domain capability architecture standards:

    • Taxonomy Rigor: PASS. 3-tier capability hierarchy covers all 4 banking divisions without gaps.
    • Ownership Clarity: PASS. KYC, Underwriting, and Clearing each assigned to a single authoritative squad.
    • Anti-Duplication: PASS. Mandatory registry intake prevents redundant builds and vendor sprawl.
    • Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to rule_markdown.md.

    Open Decisions

    • DEC-CAPARCH-01: David O'Reilly to determine whether automated CI pipeline linters should query the capability catalog to reject repositories missing capability tags (Owner: David O'Reilly).

    Next steps

    1. Elena Rostova publishes the Level 1–3 enterprise capability taxonomy to the developer portal.
    2. Architecture Guild conducts audit mapping all 180 active microservices to their supporting capability IDs.
    3. Establish quarterly capability review board evaluating maturity heatmaps ahead of budget planning.

    skill: domain-capability-architect

    Enterprise Banking Capability Architecture — Fitness Self-Check [CAPARCH-FIT-001]

    Summary

    This fitness self-check evaluates the enterprise domain capability architecture against three critical red-capable domain failure probes: anemic model, cross-context transaction, and duplicate language. All targeted probes pass by design construction. A self-check is supporting evidence, never the authoritative gate. Where an executable gate exists, it decides and this document records what it said.

    Detailed Description

    Criterion [FIT-n]ProbeEvidenceResultLimits of the claim
    FIT-1: Anemic ModelSeed a capability realization proposal where business invariants are delegated to an external orchestration script rather than the capability domain model.Capability architecture review check probe_capability_encapsulation verifying rejection of anemic implementations with diagnostic ERR_CAPABILITY_MODEL_ANEMIC.passConfirms architecture review gate; does not inspect individual developer unit test code.
    FIT-2: Cross-Context TransactionSeed an implementation where the Lending capability directly mutates database tables owned by the Payment Clearing capability.Database connection pool validator probe_capability_storage_isolation verifying transaction abort with diagnostic ERR_CROSS_CAPABILITY_DATABASE_MUTATION.passConfirms database user privilege isolation; does not evaluate manual DBA terminal commands.
    FIT-3: Duplicate LanguageSeed an initiative proposing a second "Identity Verification" capability under the Wealth Management division.Capability registry conflict linter probe_duplicate_capability_registration verifying rejection with diagnostic ERR_DUPLICATE_CAPABILITY_PROPOSAL.passConfirms enterprise catalog uniqueness checks; does not inspect internal developer slack channels.

    Residual Risk

    • Temporary organizational friction when centralizing previously siloed product capabilities under a single owning team. Accepted by David O'Reilly with executive leadership sponsorship.

    Traceability

    ClaimClassificationSourceFreshness
    Rejection of anemic modelsderivedFIT-1 probe result2026-09-15
    Rejection of cross-capability DB mutationsderivedFIT-2 probe result2026-09-15
    Rejection of duplicate capabilitiesderivedFIT-3 probe result2026-09-15

    Verification

    No validator was supplied, so no command was run.

    Open Decisions

    None.

    Next steps

    1. Architecture Guild incorporates capability metadata checks into repository onboarding templates.
    2. Platform team maps all 180 services to the central capability registry.
    3. Conduct quarterly capability review board evaluating maturity heatmaps ahead of budget planning.

    domain-capability-portfolio-architect.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Define 3-tier business capability hierarchiesClassify core, supporting, and generic subdomainsMap essential complexity versus strategic valueIdentify domain boundaries from business outcomesDirect R&D investment using maturity heatmaps

    About this skill

    What it does

    This skill defines the problem-space portfolio within an accepted business domain. It identifies coherent abilities the domain must possess, groups related behavior and knowledge into subdomain hypotheses, records outcomes and scope, classifies their current strategic role, distinguishes essential domain complexity from accidental implementation complexity, and directs where deeper domain modeling and learning investment are justified.

    Use it when

    • Derive domain-capability and subdomain hypotheses from accepted outcomes, decisions, rules, scenarios, language, events, policies, and domain-owner evidence
    • Define a domain/subdomain's purpose, actors, outcomes, knowledge, behavioral scope, exclusions, dependencies, and owner
    • Distinguish one coherent capability from process stages, technical functions, duplicated labels, or implementation artifacts
    • Classify a subdomain or coherent capability group as current core, supporting, generic, unclassified, or disputed
    • Challenge core inflation, “critical means core,” “complex means core,” “we built it means core,” or permanent classification
    • Assess business differentiation separately from essential model complexity and accidental technical complexity

    For example: “Our team classified credit risk scoring, document printing, and user authentication all as core subdomains, so leadership allocated equal engineering headcount to building a custom PDF generator.”

    What you get

    • architecture/domain-capability-architect/README.md
    • architecture/domain-capability-architect/00-overview/domain-capability-architect-overview.md
    • architecture/domain-capability-architect/verification/fitness-self-check.md

    Plus one page per business module, only where your evidence calls for it: {module}/aggregates.md, {module}/domain-events.md, {module}/invariants.md, {module}/policies.md.

    All paths are relative to the output folder you choose.

    What it will not do

    Do not use for an enterprise capability map, bounded-context/service decomposition, implementation ownership, build-vs-buy selection, or classifying from code nouns alone.

    How it works

    1. Check solution space boundaries.
    2. Identify domain capabilities.
    3. Form subdomain hypotheses.
    4. Assess business differentiation.
    5. Assess essential complexity.
    6. Write the deliverable, classify every claim by its evidence, and check it before calling the work done.

    What's in the package

    Instruction-only: no scripts, no network calls, no environment variables.

    • LICENSE.txt
    • SKILL.md
    • agents/openai.yaml
    • assets/output-template-artifact.md
    • assets/output-template-contract.md
    • assets/output-template-decision.md
    • assets/output-template-domain.md
    • assets/output-template-fitness.md
    • assets/output-template-mechanism.md
    • references/domain-rules.md
    • references/operating-rules.md
    • references/output-contract.md

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 12 days ago

    • Passed all security checks, Safe to install

    Listed12 days ago

    What's inside

    Frequently Asked Questions