map-subdomains

Name: map-subdomains
Availability: InStock
Author: Foomakers

Analyze PRDs and initiatives to classify DDD subdomains and generate specification files.

6|Updated Aug 3, 2025

Search Tags:#ddd #domain-driven design #prd #subdomain #adoption files #business capability

Ready to run

npx skills add https://github.com/foomakers/pair --skill map-subdomains

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: map-subdomains
Source: https://github.com/foomakers/pair/tree/main/packages/knowledge-hub/dataset/.skills/process/map-subdomains
Command: npx skills add https://github.com/foomakers/pair --skill map-subdomains

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of translating product requirements and strategic initiatives into well-defined Domain-Driven Design (DDD) subdomains, creating essential adoption files for your project.

Core Features & Use Cases

DDD Subdomain Definition: Analyzes PRDs and initiatives to identify and classify subdomains as Core, Supporting, or Generic.
Automated File Generation: Creates structured .md files for each new subdomain in the adoption/product/subdomain/ directory, using a predefined template.
Idempotent Operation: Detects existing subdomain files and creates only the missing ones, ensuring consistency and preventing duplicates.
Use Case: After defining your product strategy in the PRD, use this Skill to automatically generate the foundational subdomain specifications, guiding your architectural decisions and team responsibilities.

Quick Start

Run the map-subdomains skill to define all subdomains based on the current PRD and initiatives.

Frequently Asked Questions about map-subdomains

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

FAQPage Schema

How do I define DDD subdomains from a PRD?▼

You can define DDD subdomains from a PRD by analyzing product requirements and strategic initiatives to classify business capabilities into core, supporting, and generic categories, generating structured specification files for architectural guidance.

What is the difference between core, supporting, and generic subdomains in domain-driven design?▼

In domain-driven design, core subdomains represent primary business differentiators, supporting subdomains provide necessary but non-differentiating capabilities, and generic subdomains offer standard utility functions, all derived directly from analyzing your PRD.

How do I generate subdomain specification files without creating duplicates?▼

Generating subdomain specification files without duplicates requires an idempotent process that detects existing files in the adoption/product/subdomain/ directory and skips them, creating only the missing markdown templates for new business capabilities.

Can I automatically classify business capabilities from product requirements?▼

You can automatically classify business capabilities from product requirements by analyzing the PRD and strategic initiatives to categorize each subdomain into core, supporting, or generic types, outputting structured adoption files.

What format do DDD subdomain specification files use in the adoption directory?▼

DDD subdomain specification files use a predefined markdown template format, generated directly into the adoption/product/subdomain/ directory to document core, supporting, and generic business capabilities for team reference.