applying-mart-candidates

To apply a mart candidate, provide the plan file and candidate-id. The Skill updates only that candidate's section within the /refactor-mart workflow, preserving all other plan sections to minimize regression risk.

The dependency gate validates scope and acceptance criteria by reading validation contracts. It ensures only approved Type: int or mart candidates are edited, while staging candidates remain strictly unchanged during the application process.

No, staging candidates remain unchanged. The Skill enforces strict plan-candidate selection, ensuring only approved Type: int or mart candidates are edited to support targeted updates within dbt mart workflows.

Applying a single approved mart candidate minimizes regression risk by isolating changes. This targeted update approach reduces unintended modifications across the dbt plan file and speeds up code reviews.

The Skill reads references and validation contracts to identify approved candidates. You provide the specific candidate-id, and it enforces that only candidates meeting the dependency gate and approval criteria are edited.

Yes, the Skill operates within /refactor-mart workflows and specifically supports dbt data modeling. It enforces that only Type: int or mart candidates with approval are edited, preserving staging layers.