What problem does it solve? Translating a domain-driven tactical model into an executable build plan is error-prone: boundaries get pinned inconsistently, parallel workers invent divergent types, and task files drift from the source of truth. This Skill derives the worker-composer's manifest directly from the model so every block and boundary is coherent before any code is written. ## Core Features & Use Cases - Model-to-manifest mapping: Converts aggregates, commands, Customer/Supplier relationships, events, and UI screens into typed blocks (aggregate, application-service, port, adapter, read-model, ui, scaffold) in building-blocks.yaml. - Boundary pinning: Enforces Published Language at every seam — pinned primitive/shared-kernel types, key minting rules, projections (in-process vs cross-deploy), contract forms (OpenAPI or event-schema), and consumer-driven contract tests. - Derived block files: Seeds one self-contained Markdown file per block into blocks/<context>/todo/ with linted completeness standards, keeping state in folder position rather than checkboxes. - Use Case: After finishing the tactical model for a ticketing feature, run this Skill to emit the manifest with pinned boundaries and tests_nl, then launch the worker-composer to build owner-first waves. ## Quick Start Ask the agent to run the build-manifest skill on the current feature to generate building-blocks.yaml and seed the block files from the tactical model.
