Domain Identification and Grouping workflow skill. Use this skill when the user needs Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis) and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Domain Identification and Grouping workflow skill. Use this skill when the user needs Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis) and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages packages/skills-catalog/skills/(architecture)/domain-identification-grouping from https://github.com/tech-leads-club/agent-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Domain Identification and Grouping This skill groups architectural components into logical domains (business areas) to prepare for creating domain services in a service-based architecture.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How to Use, Core Concepts, Identified Domains, Component Domain Assignment, Namespace Refactoring Plan, Domain Map.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
After identifying, sizing, and analyzing component dependencies
Before creating domain services (Pattern 6)
When planning service-based architecture migration
Analyzing component relationships and business alignment
Preparing for domain-driven design implementation
Grouping components for better organization
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
QUICK-REFERENCE.md
Starts with the smallest copied file that materially changes execution
Supporting context
README.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
How do components relate to business capabilities?
Collaborate with Business Stakeholders
Validate domain identification with product owners
Ensure domains align with business understanding
Get feedback on domain boundaries
Example Domain Identification:
#### Imported: Next Steps
After creating component domains:
1.**Apply Create Domain Services Pattern** - Extract domains to separate services
2.**Plan Service Extraction** - Create migration plan for domain services
3.**Implement Domain Services** - Move domains to separately deployed services
4.**Monitor Domain Boundaries** - Use fitness functions to enforce boundaries
#### Imported: How to Use### Quick Start
Request analysis of your codebase:
-**"Group components into logical domains"**-**"Identify component domains for service-based architecture"**-**"Create domain groupings from components"**-**"Analyze which components belong to which domains"**### Usage Examples**Example 1: Domain Identification**
User: "Group components into logical domains"
The skill will:
Analyze component responsibilities and relationships
Identify business domains based on functionality
Group components into domains
Create domain diagrams
Suggest namespace refactoring for domain alignment
**Example 2: Domain Analysis**
User: "Which domain should the billing components belong to?"
The skill will:
Analyze billing component functionality
Check relationships with other components
Identify appropriate domain (e.g., Customer or Financial)
Recommend domain assignment
**Example 3: Domain Refactoring**
User: "What namespace refactoring is needed to align components with domains?"
The skill will:
Compare current component namespaces to identified domains
Identify misaligned components
Suggest namespace changes
Create refactoring plan
### Step-by-Step Process
1. **Identify Domains**: Analyze business capabilities and component relationships
2. **Group Components**: Assign components to appropriate domains
3. **Validate Groupings**: Ensure components fit well in their domains
4. **Refactor Namespaces**: Align component namespaces with domains
5. **Create Domain Map**: Visualize domain structure and component groupings
## Examples
### Example 1: Ask for the upstream workflow directly
```text
Use @domain-identification-grouping to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @domain-identification-grouping against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @domain-identification-grouping for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @domain-identification-grouping using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Collaborate with business stakeholders to identify domains
Group components by business capability, not technical layers
Ensure domains represent distinct business areas
Validate domain boundaries with stakeholders
Refactor namespaces to align with domains
Create clear domain documentation
Use business language in domain names
Imported Operating Notes
Imported: Best Practices
Do's ✅
Collaborate with business stakeholders to identify domains
Group components by business capability, not technical layers
Ensure domains represent distinct business areas
Validate domain boundaries with stakeholders
Refactor namespaces to align with domains
Create clear domain documentation
Use business language in domain names
Don'ts ❌
Don't create domains based on technical layers (services, controllers, models)
Don't force components into domains where they don't fit
Don't skip stakeholder validation
Don't create too many small domains (aim for 3-7 domains)
Don't create domains that are too large (monolithic domains)
Don't ignore components that don't fit (analyze why)
Don't skip namespace refactoring (critical for clarity)
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in packages/skills-catalog/skills/(architecture)/domain-identification-grouping, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@accessibility - Use when the work is better handled by that native specialization after this imported skill establishes context.
@ai-cold-outreach - Use when the work is better handled by that native specialization after this imported skill establishes context.
@ai-pricing - Use when the work is better handled by that native specialization after this imported skill establishes context.
@ai-sdr - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
Notice how all customer-related functionality is grouped under .customer domain.
Imported: Identified Domains
Ticketing Domain (ss.ticket)
Ticket creation, assignment, routing, completion
Customer surveys
Knowledge base
Customer Domain (ss.customer)
Customer profile
Billing and payment
Support contracts
Reporting Domain (ss.reporting)
Ticket reports
Expert reports
Financial reports
Admin Domain (ss.admin)
User maintenance
Expert profile management
Shared Domain (ss.shared)
Login
Notification
### Phase 2: Group Components into Domains
Assign each component to an appropriate domain:
1. **Analyze Component Functionality**
- What business capability does it support?
- What domain vocabulary does it use?
- What other components does it relate to?
2. **Check Component Relationships**
- Which components are frequently used together?
- What are the dependencies between components?
- Do components share data or workflows?
3. **Assign to Domain**
- Place component in domain that best fits its functionality
- Ensure component aligns with domain's business language
- Verify component relationships support domain grouping
4. **Handle Edge Cases**
- Components that don't fit clearly: Analyze more deeply
- Components that fit multiple domains: Choose primary domain
- Shared components: May belong to Shared domain
**Example Component Grouping**:
```markdown
#### Imported: Component Domain Assignment
### Ticketing Domain (ss.ticket)
- Ticket Shared (ss.ticket.shared)
- Ticket Maintenance (ss.ticket.maintenance)
- Ticket Completion (ss.ticket.completion)
- Ticket Assign (ss.ticket.assign)
- Ticket Route (ss.ticket.route)
- KB Maintenance (ss.ticket.kb.maintenance)
- KB Search (ss.ticket.kb.search)
- Survey (ss.ticket.survey)
### Customer Domain (ss.customer)
- Customer Profile (ss.customer.profile)
- Billing Payment (ss.customer.billing.payment)
- Billing History (ss.customer.billing.history)
- Support Contract (ss.customer.supportcontract)
### Reporting Domain (ss.reporting)
- Reporting Shared (ss.reporting.shared)
- Ticket Reports (ss.reporting.tickets)
- Expert Reports (ss.reporting.experts)
- Financial Reports (ss.reporting.financial)
Phase 3: Validate Domain Groupings
Ensure components fit well in their assigned domains:
Check Cohesion
Do components in domain share business language?
Are components frequently used together?
Do components have direct relationships?
Verify Boundaries
Are domain boundaries clear?
Do components belong to only one domain?
Are there components that don't fit anywhere?
Assess Completeness
Are all components assigned to a domain?
Are domains cohesive and well-formed?
Do domains represent distinct business capabilities?
Get Stakeholder Validation
Review domain groupings with product owners
Ensure domains align with business understanding
Get feedback on domain boundaries
Validation Checklist:
All components assigned to a domain
Domains have clear boundaries
Components fit well in their domains
Domains represent distinct business capabilities
Stakeholders validate domain groupings
Phase 4: Refactor Namespaces for Domain Alignment
Align component namespaces with identified domains:
