pair-process-map-subdomains

Classify DDD subdomains from PRDs and generate missing specification files.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill pair-process-map-subdomains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pair-process-map-subdomains
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-process-map-subdomains
Command: npx skills add https://github.com/foomakers/pair --skill pair-process-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, ensuring a clear and structured approach to software architecture.

Core Features & Use Cases

  • Automated Subdomain Identification: Analyzes PRDs and initiatives to identify core business capabilities.
  • DDD Classification: Classifies identified capabilities as Core, Supporting, or Generic.
  • Adoption File Generation: Creates structured .md files for each subdomain in the adoption/product/subdomain/ directory, following a predefined template.
  • Idempotent Operation: Detects existing subdomain files and creates only the missing ones, preventing duplication.
  • Use Case: After defining a new product feature in the PRD, run this Skill to automatically generate the necessary subdomain specifications, ensuring architectural alignment from the start.

Quick Start

Run the pair-process-map-subdomains skill to define all subdomains based on the current PRD.

Frequently Asked Questions about pair-process-map-subdomains

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

FAQPage Schema
How do I define DDD subdomains from a product requirement document?

To define DDD subdomains from a PRD, this Skill analyzes product requirements and strategic initiatives to identify business capabilities and classify them. It automatically generates structured specification files for each identified subdomain.

Can I automatically classify subdomains as core, supporting, or generic from my PRD?

Yes, you can classify subdomains as core, supporting, or generic directly from your PRD. The Skill evaluates product requirements to categorize business capabilities and generates corresponding specification files in the adoption directory.

What is the best way to generate domain-driven design specification files for new product features?

The best way to generate DDD specification files is to run this Skill after defining a new product feature. It creates structured markdown files in the adoption/product/subdomain directory using a predefined template, ensuring architectural alignment.

How do I prevent duplicate subdomain files when regenerating architecture specifications?

To prevent duplicate subdomain files during specification generation, the process runs idempotently. It detects existing subdomain files and creates only the missing ones, ensuring no duplication occurs across multiple executions.

Do I need a specific template format to map subdomains from strategic initiatives?

You need a provided template format to map subdomains from strategic initiatives. The Skill uses this predefined template to generate structured markdown specification files within the adoption/product/subdomain directory.

How does analyzing strategic initiatives help identify core business capabilities for software architecture?

Analyzing strategic initiatives helps identify core business capabilities by translating product requirements into well-defined Domain-Driven Design subdomains. This ensures a clear and structured approach to software architecture from the start.