Claude Ddd Redesign

    2

    Domain-Driven Modernization: re-decompose N services into M bounded-context-aligned services with no unadjudicated behavioral change.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    claude-ddd-redesign

    Example session with this skill installed

    I need to define a new modernization slice for the Billing service. Create the initial slice outline and size estimation artifacts based on Behaviors BHV-1021 and BHV-1022.

    • Read your context and instructions
    • Compiled the claude-ddd-redesign

    I have initialized the Slice Outline and Size estimation artifacts for the new Billing modernization slice. These files are grounded in the provided Behavior IDs and follow the Stage 3 schema requirements.

    Modernization Slice: SLC-0042 (Billing)

    slices/SLC-0042/slice.json

    {
  "id": "SLC-0042",
  "workstream": "WS-0005",
  "oracle_strategy": "characterization",
  "behaviors": ["BHV-1021", "BHV-1022"],
  "state": "draft"
}

    slices/SLC-0042/size.json

    {
  "slice": "SLC-0042",
  "behaviors": 2,
  "interfaces_sync": 1,
  "interfaces_async": 0,
  "complexity_factors": [
    "cross-service-invariant-validation"
  ]
}

    Next steps

    1. Review the behavior citations to ensure BHV-1021 and BHV-1022 cover all necessary billing invariants.
    2. Define the acceptance-criteria.json for this slice to map specific assertions to these behaviors.
    3. Update the roadmap.json to include this slice in the next delivery increment.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Modernizing legacy monoliths into distributed services often fails due to behavior drift and untraceable requirements. This skill package provides a rigorous, schema-driven framework for Domain-Driven Design (DDD) redesign, ensuring every service boundary is grounded in observed behavior rather than guesswork.

    What it does

    • Inventories behavior by extracting and classifying atomic facts from legacy code to maintain functional parity.
    • Models domains using strategic context maps and tactical aggregate models to define strict service boundaries.
    • Automates traceability by linking acceptance criteria and characterization tests directly to specific behavior IDs.
    • Manages migration through structured cutover plans, retirement registers, and multi-team migration waypoints.
    • Formalizes decisions using Architecture Decision Records (ADRs) and human-adjudicated consensus runs.

    How it works

    1. Initialize the inventory by running discovery agents to populate behavior.json and interfaces.json from the legacy source.
    2. Draft the model using contexts.json to define bounded contexts and divergences.json to flag conceptual conflicts between services.
    3. Sequence delivery by creating a roadmap.json that prioritizes the walking skeleton and manages capacity constraints.
    4. Define slices for incremental modernization, generating tactical-model.json and design.md for each deployable unit.
    5. Execute transition following the cutover-plan.json steps from shadow mode through to final decommissioning.

    Frameworks & tools

    This tool uses JSON Schema for all artifact validation. It integrates with Python-based linting scripts like trace-lint.py and resolve-identity.py.

    Why this beats prompting it yourself

    Generic prompts fail to maintain the strict traceability required for high-stakes refactoring. This skill enforces a schema-valid "spine" that connects legacy behavior to new implementation, preventing the silent loss of edge-case logic during service extraction.

    Use cases

    • Decomposing a monolithic Java or .NET application into Bounded Contexts.
    • Identifying and resolving domain logic divergences across different business units.
    • Managing long-running consumer migrations during interface retirement.
    • Generating a verifiable characterization suite for legacy system replacement.

    Known limitations

    Does not automate behavior extraction; relies on external discovery agents and manual review. Requires a human decider for all architectural adjudications.

    What's included (18 skills in this plugin)

    • acceptance-criteria

      Defines the content and structure of a Slice's Acceptance Criteria. Reference when assembling or reviewing slices/<id>/acceptance-criteria.json.

    • adjudication-record

      Defines the content and structure of Consensus Run and Adjudication records — the mechanical ensemble output and the accountable human decision over it. Reference when writing to consensus/*.json or adjudications/*.json.

    • adr

      Defines the content and structure of an Architecture Decision Record. Reference when assembling or reviewing adr/*.md.

    • behavior-inventory

      Defines the content and structure of the Behavior Inventory — the unit of traceability for the whole method. Reference when assembling or reviewing inventory/behaviors.json.

    • characterization-suite

      Defines the content and structure of a Slice's characterization test suite. Reference when assembling or reviewing slices/<id>/verification/characterization/*.

    • context-model

      Defines the content and structure of the Modeled Context and Context Map — the Stage 2 Strategic Design output. Reference when assembling or reviewing model/contexts.json and model/context-map.json.

    • contract-tests

      Defines the content and structure of consumer-driven contract tests for a Slice's interfaces. Reference when assembling or reviewing slices/<id>/verification/contracts/*.

    • cutover-plan

      Defines the content and structure of a Context's cutover plan — Stage 8 Transition's shadow/canary/cutover/decommission sequencing. Reference when assembling or reviewing contexts/<id>/cutover-plan.json.

    • design-doc

      Defines the content and structure of a Slice's detailed design document. Reference when assembling or reviewing slices/<id>/design.md.

    • divergence-register

      Defines the content and structure of the Divergence Register — places where two or more services disagree about the same concept. Reference when assembling or reviewing inventory/divergences.json.

    • interface-inventory

      Defines the content and structure of the Interface Inventory — synchronous endpoints and asynchronous streams, published and consumed. Reference when assembling or reviewing inventory/interfaces.json.

    • migration-waypoints

      Defines the content and structure of Migration Waypoints — dated Consumer Migration Workstream checkpoints tying specific teams' readiness to legacy Interface retirement. Reference when assembling or reviewing migration-waypoints.json.

    • observability-spec

      Defines the content and structure of a Slice's observability specification. Reference when assembling or reviewing slices/<id>/verification/observability-spec.md.

    • retirement-register

      Defines the content and structure of the Retirement Register — every legacy Interface, its known consumers, and its sunset status. Reference when assembling or reviewing retirement.json.

    • roadmap

      Defines the content and structure of the Delivery Roadmap — Stage 4's Increment sequencing, capacity model, and forecast. Reference when assembling or reviewing roadmap.json.

    • slice-outline

      Defines the content and structure of a Slice record and its Size — the Stage 3 Solution Outline unit of delivery. Reference when assembling or reviewing slices/<id>/slice.json and size.json.

    • tactical-model

      Defines the content and structure of a Slice's Tactical Model — aggregates, invariants, domain events, commands, and policies. Reference when assembling or reviewing slices/<id>/tactical-model.json.

    • variation-policy

      Defines the content and structure of a Variation Policy — formalizing a Divergence classified 'policy' as explicit, intentional domain variation. Reference when assembling or reviewing model/variation-policy.json.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean 2 days ago

    • Passed all security checks, Safe to install

    Requires

    Python
    Git

    Listed2 days ago

    What's inside

    Frequently Asked Questions