subdomain-distillation

Classify software subdomains into Core, Supporting, or Generic categories.

1|Updated Jun 20, 2026

Search Tags:#architecture #ddd #domain-modeling #distillation #subdomain #strategic-design

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill subdomain-distillation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subdomain-distillation
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/subdomain-distillation
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill subdomain-distillation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill prevents the common and costly mistake of misallocating modeling effort by helping teams distinguish between Core, Supporting, and Generic subdomains.

Core Features & Use Cases

Strategic Classification: Apply industry-standard heuristics like the Outsource Test and Wardley Evolution to categorize business domains.
Security-Sensitivity Analysis: Identify critical slices of a domain that require high-rigor modeling regardless of their general classification.
Legacy Transformation: Sequence modernization efforts by prioritizing Core domains while identifying Generic candidates for replacement.

Quick Start

Use the subdomain-distillation skill to analyze the current product architecture and generate a classification canvas for each identified subdomain.

Frequently Asked Questions about subdomain-distillation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I classify subdomains for domain-driven design?▼

To classify subdomains for domain-driven design, you categorize business domains into Core, Supporting, or Generic types using heuristics like the Outsource Test and Wardley Evolution, aligning modeling investment with actual business value.

What is the difference between Core, Supporting, and Generic subdomains?▼

Core subdomains provide competitive differentiation requiring high modeling effort, Supporting subdomains are necessary but not differentiators, and Generic subdomains are universal needs often suitable for off-the-shelf solutions or outsourcing.

How do I sequence legacy modernization efforts using strategic design?▼

Sequence legacy modernization by prioritizing Core domains for high-rigor modeling and transformation, while identifying Generic subdomains as primary candidates for replacement using off-the-shelf solutions to optimize resource allocation.

Can I apply domain-driven design distillation to security-sensitive domains?▼

Yes, you can apply domain-driven design distillation to security-sensitive domains by identifying critical slices within the architecture that require high-rigor modeling regardless of their general Core, Supporting, or Generic classification.

When should I not invest heavily in modeling a supporting subdomain?▼

You should avoid heavy modeling investment in a supporting subdomain when it passes the Outsource Test or maps to a highly evolved Wardley Evolution stage, indicating it is a generic commodity better served by off-the-shelf solutions.