pair-process-map-contexts

Generate bounded context definitions and integration patterns from a subdomain catalog.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill pair-process-map-contexts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pair-process-map-contexts
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-process-map-contexts
Command: npx skills add https://github.com/foomakers/pair --skill pair-process-map-contexts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill automates the creation of bounded context definitions within a software architecture, translating business subdomains into clear technical boundaries and integration strategies.

Core Features & Use Cases

  • Automated Context Generation: Creates .md files for bounded contexts based on subdomain analysis and architectural guidelines.
  • Integration Pattern Mapping: Defines how different contexts will communicate (synchronous, asynchronous, etc.).
  • Use Case: After defining your business subdomains, use this Skill to automatically generate the foundational documentation for each bounded context, including its scope, responsibilities, and integration points, ensuring architectural consistency.

Quick Start

Run the pair-process-map-contexts skill to define all bounded contexts based on the current subdomain catalog.

Frequently Asked Questions about pair-process-map-contexts

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

FAQPage Schema
How do I generate bounded contexts from subdomains for domain-driven design?

To generate bounded contexts from subdomains, this Skill maps your subdomain catalog and architectural constraints to produce context files with defined integration patterns. It creates foundational documentation in the `adoption/tech/boundedcontext/` directory.

What is context mapping and how does it define integration patterns for bounded contexts?

Context mapping defines how different bounded contexts communicate by specifying integration patterns like synchronous or asynchronous communication. This Skill translates business subdomains into clear technical boundaries and maps their integration strategies.

How do I automate bounded context documentation creation without overwriting existing files?

Automating bounded context documentation creation is idempotent with this Skill, meaning it only generates missing context files. It creates `.md` files for each context based on your subdomain analysis without overwriting existing definitions.

Do I need a subdomain catalog before defining bounded contexts?

Yes, you need an existing subdomain catalog and architectural guidelines before defining bounded contexts. This Skill processes that catalog to map subdomains to contexts and specify their scope, responsibilities, and integration points.

What's the best way to establish architectural consistency across multiple bounded contexts?

Establishing architectural consistency across bounded contexts is done by generating standardized adoption files. This Skill ensures all contexts follow the same architectural constraints and integration pattern definitions derived from your subdomain analysis.