What problem does it solve? When working on a data modeling change, you often need to verify how existing specs, YAML models, or SQL files actually behave before deciding on a fix. This Skill reads the relevant repository files for a named change and records structured findings directly into design.md, so investigation results are never lost. ## Core Features & Use Cases - Targeted file reading: Prioritizes spec-model.yaml, design.md, spec.md, referenced table specs, and SQL/dbt model files relevant to the request. - Structured finding reports: Produces a summary with files read, findings, impact, and a recommended next action. - Persistent findings log: Appends dated findings to a ## Findings section in design.md for the active change. - Use Case: While implementing a dbt model change, you suspect a column mismatch between spec-model.yaml and the SQL file. Run the investigation, and the Skill documents the discrepancy and recommends whether to fix inline, re-run design, or update the spec. ## Quick Start Ask the assistant to investigate why the column names in spec-model.yaml differ from the dbt model for the current change and record the finding in design.md.
