bounded-context-analyzer

Analyzes service repositories to generate a canonical context.md document.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill bounded-context-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bounded-context-analyzer
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/bounded-context-analyzer
Command: npx skills add https://github.com/joleques/northstar-ai --skill bounded-context-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill analyzes multiple service repositories under a target directory to produce a canonical context document that unifies architectural data with business domain knowledge.

Core Features & Use Cases

  • Identify services and boundaries within a services/ folder.
  • Extract the ubiquitous language, domain aggregates, and integration boundaries to build context.md.
  • Generate a single source of truth that aligns business and technical perspectives for bounded contexts.

Quick Start

Run the bounded-context-analyzer on a workspace containing a services/ directory to generate the context.md.

Frequently Asked Questions about bounded-context-analyzer

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

FAQPage Schema
How do I analyze bounded contexts across multiple service repositories?

Analyzing bounded contexts across multiple services involves scanning a services/ directory to extract domain language, aggregates, and integration boundaries to generate a unified context.md document.

What is the best way to extract domain language and aggregates from a multi-service architecture?

The best way to extract domain language and aggregates is to map the code and configurations without modifying sources, producing a canonical context document that aligns business and technical perspectives.

How do I generate a context.md file for DDD architecture analysis?

You generate a context.md file for DDD architecture analysis by running an analyzer on a workspace containing a services/ directory to identify domain boundaries and map the ubiquitous language.

Does bounded context analysis modify my source code during domain mapping?

Bounded context analysis does not modify your source code; it strictly reads code and configurations to output a structured context.md document mapping the domain boundaries.

Can I unify architectural data with business domain knowledge for multi-service workflows?

You can unify architectural data with business domain knowledge by identifying integration boundaries across services to build a single source of truth context.md document.