ddd-arch-planner

name

ddd-arch-planner

description

Multi-review architecture planning skill for DDD / Clean Architecture .NET projects. Produces a versioned, implementation-ready architecture document through a structured review pipeline (database → security → backend), culminating in a Claude Code–ready implementation plan with Definition of Done, migration gates, and security debt tracking. ACTIVATE at the END of an architecture design session when the user asks for: "implementációs terv", "Claude Code-nak szánt terv", "implementation plan", "generáld le a tervet", "készítsd el a tervdokumentumot", "következő sprint architektúra", "architecture phase plan", "next phase architecture", "design + review + DoD", or any variant of "make it ready for implementation" / "következő fázis terve". Do NOT activate for single-question architecture answers — only for the full multi-review pipeline that produces a shippable implementation document.

DDD Architecture Planner

Structured multi-review pipeline that turns an architecture discussion into a versioned, implementation-ready document for Claude Code execution.

---

1. When to use this skill

You are in the right place when ALL of these are true:

• A new backend feature / phase / module is being designed
• The stack is .NET (Clean Architecture + DDD + CQRS) with PostgreSQL
• The output will be handed to Claude Code (or another agent) for implementation
• The user wants a DoD checklist, migration plan, and security gate list

You are in the wrong place if:

• The user wants a quick answer to a single design question → answer directly
• The stack is not .NET / DDD → adapt or use /senior-architect instead

---

2. The pipeline

Phase 0 — Context load
  └─ Read project knowledge, existing architecture docs, security debt register

Phase 1 — v1 Draft
  └─ Domain model · DB schema · API surface · Value Objects
     Output: {document}_v1.md

Phase 2 — Database review
  📂 Load: references/sub-database-designer.md + references/sub-database-schema-designer.md
  └─ Findings → v2 delta table
     Output: {document}_v2.md

Phase 3 — Security review
  📂 Load: references/sub-senior-security.md
  └─ Findings → v3 delta table (CRITICAL / HIGH / MEDIUM)
     Output: {document}_v3.md

Phase 4 — Backend review
  📂 Load: references/sub-senior-backend.md
  [optional — trigger if >= 1 HIGH finding remains after v3]
  └─ Findings → v4 delta table
     Output: {document}_v4.md

Phase 5 — Final document assembly
  └─ Cumulative Finding Summary · DoD checklist · Security debt table · Roadmap · Status banner