implementation-blueprint

Map DDD outputs into a deterministic backend monolith folder structure.

1|Updated Feb 12, 2026

Search Tags:#architecture #monolith #decision-log #folder-structure #context-map #ddd-workshop #bc-communication

Ready to run

npx skills add https://github.com/dev-goraebap/grimoire --skill implementation-blueprint-dev-goraebap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-blueprint
Source: https://github.com/dev-goraebap/grimoire/tree/main/ddd-workshop/skills/implementation-blueprint
Command: npx skills add https://github.com/dev-goraebap/grimoire --skill implementation-blueprint-dev-goraebap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

팀 간 DDD 산출물(context-map, _canvas, aggregate 명세)이 서로 다르게 폴더 구조로 해석되는 문제를 해결하기 위해, 인터뷰 기반으로 백엔드 모놀리스 구조와 레이어 경계, BC 간 통신 방식까지 명시된 단일 블루프린트를 생성합니다.

Core Features & Use Cases

DDD 산출물을 구체적 모놀리식 프로젝트 레이아웃으로 변환하고 도메인 경계를 폴더 구조에 반영합니다.
BC 경계와 통신 정책을 캡처하여 교차 BC 결합을 방지하고 팀 간 합의를 촉진합니다.
의사결정 근거, 대안, 안티패턴 체크리스트를 기록하는 유지보수 가능한 산출물을 만듭니다. 실무 예시: 서로 다른 팀이 제시한 폴더 구조를 하나의 확정된 구조로 합의해 온보딩과 협업 효율을 높입니다.

Quick Start

Provide your DDD context maps and aggregate docs to generate a concrete monolith layout with BC boundaries.

Frequently Asked Questions about implementation-blueprint

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

FAQPage Schema

How do I convert DDD context maps and aggregate specs into a consistent monolith folder structure?▼

To convert DDD context maps into a monolith folder structure, this Skill maps context maps, canvas, and aggregate specs into a deterministic backend layout with clear boundaries, layers, and inter-BC interaction rules. It ensures uniform structure across projects by applying consistent architecture decisions.

How do I define BC communication rules to prevent cross-BC coupling in a monolithic architecture?▼

Defining BC communication rules in a monolithic architecture requires capturing explicit boundaries and interaction policies. This Skill generates a blueprint that enforces cross-BC JOIN policies and repository interfaces, preventing unwanted coupling and promoting team consensus across multiple bounded contexts.

What is the best way to document architecture decisions like ORM selection and DB strategy for a DDD monolith?▼

The best way to document architecture decisions is by capturing them as explicit records with rationale, alternatives, and anti-pattern checks. This Skill records runtime choices, ORM selection, DB strategy, and query usage to create maintainable architecture decision logs for your DDD monolith.

Can I use this to standardize backend project layouts across different teams and scopes?▼

Yes, you can standardize backend project layouts across teams. This Skill applies consistent architecture decisions across multiple documents and scopes, ensuring uniform folder structure and layer boundaries so different teams align on a single, agreed-upon monolith blueprint.

When do I need a deterministic monolith blueprint for my DDD outputs?▼

You need a deterministic monolith blueprint when DDD outputs like context maps and aggregate specs are interpreted differently into folder structures by separate teams. This Skill resolves those discrepancies by generating a single, agreed layout with clear folder structure and BC communication rules.