What problem does it solve? It bridges the gap between domain modeling and implementation by automatically deriving an authoritative build manifest (building-blocks.yaml) from a tactical DDD model, eliminating hand-written task lists that silently diverge from the architecture. ## Core Features & Use Cases - Model-to-manifest derivation: Maps aggregates, commands, Customer/Supplier relationships, events, and UI screens to typed blocks (aggregate, application-service, port, adapter, read-model, ui, scaffold) with pinned boundary types and projections. - Boundary contract pinning: Enforces Published Language at every seam, pins key minting rules, delivery guarantees, contract forms (OpenAPI or event-schema), and §14 invariant gates so parallel workers compose without inventing architecture. - Incremental regeneration: Re-runs as a delta-only refresh once the build is running, updating only impacted derived block files while preserving worker state and previously elicited tests_nl. - Use Case: After completing the tactical model for a feature, run this Skill to emit the manifest and per-block spec files that the worker-composer's readiness gate consumes to orchestrate the build waves. ## Quick Start Run the build-manifest skill on my feature after the architecture is decided to generate building-blocks.yaml and the block files for the worker-composer.
