domain-extractor
Extract technology-free domain model from codebase. Produces a pure business-language specification that any stakeholder can understand. Use for: understand legacy code, document business logic, domain modeling, business requirements extraction, what does this code do, explain codebase to non-technical stakeholders.
When & Why to Use This Skill
This Claude skill specializes in extracting technology-free domain models from complex codebases, producing pure business-language specifications. It bridges the gap between technical implementation and business requirements by translating code into concepts that stakeholders, such as CEOs and Product Managers, can easily understand. Ideal for documenting legacy systems, extracting business rules, and facilitating domain-driven design without the noise of technical jargon like APIs, databases, or specific programming syntax.
Use Cases
- Legacy System Analysis: Decipher the business logic hidden within old or poorly documented codebases to inform modernization or migration strategies.
- Executive Summaries: Provide non-technical stakeholders with a clear, high-level overview of system functionality, focusing on business value rather than implementation details.
- Domain-Driven Design (DDD): Accelerate the creation of domain models by automatically identifying core entities, actors, and workflows from existing source code.
- Knowledge Transfer: Simplify the onboarding process for new team members and product owners by providing a high-level business map of the software's purpose and rules.
| name | domain-extractor |
|---|---|
| description | > |
| specification that any stakeholder can understand. Use for | understand legacy code, |
Domain Extractor
Extract pure business domain from code. Output contains ZERO technology terms.
Purpose
Transform code into a business specification that:
- A CEO can understand
- Survives technology changes
- Captures what the system DOES, not HOW
Activation
- "What does this codebase do?"
- "Extract the business logic"
- "Document this for stakeholders"
- "I need to understand this legacy system"
Process
Step 1: Analyze Code (10-15 min)
Read the codebase looking for:
- Models/Entities → Domain concepts
- Validation → Business rules
- Controllers/Handlers → Workflows
- Error messages → User expectations
Step 2: Translate to Business Language
Forbidden terms (if you write these, rewrite):
API, REST, GraphQL, HTTP, endpoint, request, response,
database, SQL, query, schema, table, cache, session, token,
component, frontend, backend, server, client, service,
function, class, method, controller, middleware
Translation examples:
| Code | Business Language |
|---|---|
POST /api/orders |
Customer places order |
SELECT * FROM users |
Look up customer |
validateCart() |
Verify order is valid |
sendEmail() |
Notify customer |
redis.cache() |
Remember for quick access |
Step 3: Produce Output
Generate this exact format:
# Domain Specification: [System Name]
## Purpose
[One paragraph: What business problem this solves]
## Actors
- **[Actor 1]**: [Role description]
- **[Actor 2]**: [Role description]
## Core Concepts
| Concept | Definition |
|---------|------------|
| [Name] | [Business meaning] |
## Workflows
### [Workflow 1 Name]
1. [Actor] [action] [object]
2. System [verifies/records/notifies] [what]
3. [Result]
### [Workflow 2 Name]
...
## Business Rules
- [Rule 1]
- [Rule 2]
## Constraints
- [Constraint 1]
- [Constraint 2]
Validation
Before delivering, verify:
- Read aloud - would a non-technical person understand every word?
- Search for forbidden terms - zero should appear
- Check completeness - all major code paths represented?
Example
See references/example.md for complete input/output example.
Output
Single markdown document: Domain Specification
No tech stack recommendations. No architecture proposals. Just pure domain.