Domain Capability Portfolio Architect
Architects business capability portfolios: 3-tier capability hierarchies, maturity heatmaps, and context mapping.
$9
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsDomain 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
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
| Criterion | Why it matters here | Weight | Source of the weight |
|---|---|---|---|
| Elimination of Duplicate Capability Build | Redundant services create massive technical debt and multi-million-dollar vendor waste (INC-4922). | 0.40 | David O'Reilly (Chief Enterprise Architect) |
| Single System of Record Authority | Each business capability must have exactly one authoritative owning team and bounded context. | 0.30 | Elena Rostova (Head of Capability Gov) |
| Capability-to-Service Traceability | Enterprise capability taxonomy must map directly to deployable microservice artifacts. | 0.15 | Core Banking Engineering SLA |
| Investment & Modernization Heatmap Clarity | Business leaders require clear visibility into capability maturity to direct quarterly budget. | 0.15 | Executive Strategy Committee |
Alternatives rejected
| Option | Why it was not taken | Under what evidence it would win |
|---|---|---|
| Ad-Hoc Squad-Led Capability Creation | Caused 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
| Concern | Owner | Handoff payload | Blocked until |
|---|---|---|---|
| Enterprise Capability Map & Taxonomy | Chief Enterprise Architect (David O'Reilly) | enterprise_capability_map_spec | Executive Committee sign-off |
| Capability Maturity Scoring & Governance | Head of Capability Gov (Elena Rostova) | capability_maturity_heatmap | Business unit review |
| Service Metadata & Capability Binding | Platform Engineering Lead | service_catalog_capability_metadata | Developer portal release |
| Capital Budget Allocation Alignment | FinOps & Portfolio Planning | it_investment_capability_alignment | Annual budget cycle |
Traceability
| Claim | Classification | Source | Freshness |
|---|---|---|---|
| 180 microservices across 4 banking divisions | provided | Enterprise scope intake | Current |
| Incident INC-4922 $1.8M duplicate KYC waste | provided | Forensic audit record | Historical |
| 3-tier capability taxonomy standard | decided | David O'Reilly & Elena Rostova | 2026-09-15 |
| Single authoritative capability ownership | decided | Architectural invariant INV-CAPARCH-01 | 2026-09-15 |
| Mandatory capability reuse intake | decided | Architectural invariant INV-CAPARCH-02 | 2026-09-15 |
| Zero orphan microservice policy | decided | Architectural invariant INV-CAPARCH-03 | 2026-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
- Elena Rostova publishes the Level 1–3 enterprise capability taxonomy to the developer portal.
- Architecture Guild conducts audit mapping all 180 active microservices to their supporting capability IDs.
- 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] | Probe | Evidence | Result | Limits of the claim |
|---|---|---|---|---|
| FIT-1: Anemic Model | Seed 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. | pass | Confirms architecture review gate; does not inspect individual developer unit test code. |
| FIT-2: Cross-Context Transaction | Seed 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. | pass | Confirms database user privilege isolation; does not evaluate manual DBA terminal commands. |
| FIT-3: Duplicate Language | Seed 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. | pass | Confirms 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
| Claim | Classification | Source | Freshness |
|---|---|---|---|
| Rejection of anemic models | derived | FIT-1 probe result | 2026-09-15 |
| Rejection of cross-capability DB mutations | derived | FIT-2 probe result | 2026-09-15 |
| Rejection of duplicate capabilities | derived | FIT-3 probe result | 2026-09-15 |
Verification
No validator was supplied, so no command was run.
Open Decisions
None.
Next steps
- Architecture Guild incorporates capability metadata checks into repository onboarding templates.
- Platform team maps all 180 services to the central capability registry.
- Conduct quarterly capability review board evaluating maturity heatmaps ahead of budget planning.
Connects securely to your tools. The creator never sees your data.
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
- Check solution space boundaries.
- Identify domain capabilities.
- Form subdomain hypotheses.
- Assess business differentiation.
- Assess essential complexity.
- 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
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
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 to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
Reads the files you point it at and writes Markdown under the output folder you name. No network access, no environment variables, and no bundled scripts.