approve-dqs

To approve a Data Quality Specification, the skill updates the DQS status to Approved, automatically records the last modified date, and appends a version history entry to clear blockers for downstream artifact creation.

The skill validates the current DQS status before proceeding to prevent duplicate approvals, ensuring the audit trail remains accurate and avoiding redundant sign-off entries for already approved documents.

You can approve a Draft-status Data Quality Specification, but the skill actively warns about un-reviewed documents to encourage proper review cycles before formally updating the status to Approved.

During the DQS approval process, the skill automatically updates three metadata fields: the document status to Approved, the last modified date, and a new entry in the version history for audit trail purposes.

Unapproved Data Quality Specification documents block data engineering workflows because teams cannot create downstream implementation artifacts like low-level designs and user stories without formal DQS sign-off.

The skill maintains a clear audit trail for data quality sign-off by validating the current status, automatically updating the DQS metadata, and appending version history entries for every approved document.