workflow-init-bounded-context

Collect service paths, create symlinks, and generate a context.md document.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishing a reliable, canonical bounded context across a codebase is often manual, error-prone, and scattered across repositories; this Skill automates collection of service paths, creation of a services/ workspace via symlinks, and generation of a consolidated context.md to make domain context explicit and machine-usable.

Core Features & Use Cases

  • Service discovery and linking: collect and validate service paths provided by the user and create predictable symlinks under services/<name>.
  • Domain context generation: run bounded-context-analyzer against the aggregated services to produce a context.md that summarizes domain concepts and boundaries.
  • Devcontainer integration: optionally run devcontainer-merger to unify .devcontainer settings for consistent development environments.
  • Use case: onboarding a microservices repository or assembling distributed service folders into a single bounded context for AI-assisted installation and documentation.

Quick Start

Run the workflow to collect service paths, create services/ symlinks, execute bounded-context-analyzer, optionally merge devcontainer settings, and output a context.md summary.

Frequently Asked Questions about workflow-init-bounded-context

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

FAQPage Schema
How do I initialize a bounded context for microservices distributed across multiple directories?

To initialize a bounded context, you collect validated filesystem paths for your services and create a services/ workspace using symlinks. This orchestrates the aggregation of distributed service folders into a single canonical context document.

What is a canonical context document and how does it make domain context machine-usable?

A canonical context document is a generated context.md file that summarizes domain concepts and boundaries. Running a bounded-context-analyzer against aggregated services makes your domain context explicit and ready for AI-driven installation flows.

Do I need permission to create symlinks when setting up a bounded context workspace?

Yes, you need validated filesystem paths and explicit permission to create symlinks to initialize the bounded context. The workflow requires these permissions to establish predictable service links under the services/ directory for domain context generation.

Can I integrate devcontainer settings when aggregating services into a bounded context?

Yes, you can optionally run devcontainer-merger to unify .devcontainer settings when initializing a bounded context. This ensures consistent development environments across the aggregated services alongside the generated context.md.

What dependencies are required to generate a bounded context document from service symlinks?

Generating a bounded context document requires the bounded-context-analyzer tool to process the symlinks. The devcontainer-merger tooling is optional for unifying development environments, but the analyzer is necessary for producing the context.md summary.