domain-analysis
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).
npx skills add tech-leads-club/agent-skills --skill domain-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Subdomain Identification & Bounded Context Analysis This skill analyzes codebases to identify subdomains (Core, Supporting, Generic) and suggest bounded contexts following Domain-Driven Design Strategic Design principles. ## When to Use Apply this skill when: - Analyzing domain boundaries in any codebase - Identifying Core, Supporting, and Generic subdomains - Mapping bounded contexts from problem space to solution space - Assessing domain cohesion and detecting coupling issues - Planning domain-driven refactoring - Understanding business capabilities in code ## Core Principles ### Subdomain Classification **Core Domain**: Competitive advantage, highest business value, requires best developers - Indicators: Complex business logic, frequent changes, domain experts needed **Supporting Subdomain**: Essential but not differentiating, business-specific - Indicators: Supports Core Domain, moderate complexity, business-specific rules **Generic Subdomain**: Common functionality, could be outsourced - Indicators: Well-understood problem, low differentiation, standard functionality ### Bounded Context An explicit linguistic boundary where domain terms have specific, unambiguous meanings. -
- When to Use
- Core Principles
- Subdomain Classification
- Bounded Context
- Analysis Process
- Phase 1: Extract Concepts
- Phase 2: Group by Ubiquitous Language
- Phase 3: Identify Subdomains
- Phase 4: Assess Cohesion
- Phase 5: Detect Low Cohesion Issues
- Phase 6: Map Bounded Contexts
- Output Format
- Domain Map
- Cohesion Matrix
What does the domain-analysis skill do?
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill domain-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.