What problem does it solve? After implementation and unit testing, teams need an internal check that code and database artifacts actually match the approved design before handing work to external QA. Without a structured self-check, unsupported alignment claims, untracked DB changes, and unrecorded assumption gaps slip through to review. ## Core Features & Use Cases - Design-Alignment Verification: Compares implemented code and DB manufacturing artifacts (DDL, migrations, stored procedures, ORM mappings, seed data, correction scripts) against approved design evidence. - Subagent Splitting for Large Scopes: Splits self-check execution by artifact family or target boundary when code, DB artifacts, tests, and design evidence exceed one context, with a coordinator merging findings. - Structured Findings and Handoff: Produces self-check results, alignment findings, unresolved item lists, and execution metrics, finalized as done, unknown, or out_of_scope before quality-group handoff. - Use Case: A team finishes a feature including schema migrations and stored procedures; run this Skill to confirm every DB artifact traces back to approved design evidence and flag unresolved assumption gaps before QA review. ## Quick Start Run the manufacturing self-check on the implemented code and DB migration artifacts against the approved design documents and unit test results, then report alignment findings and unresolved items.
