linear-delivery-traceability

To enforce Linear traceability, this Skill intercepts progress reporting and issue state updates, rejecting claims unless they include verifiable artifacts, exact file paths, correct issue linkage, and coherent project status.

Artifact verification for project delivery works by checking that AI progress reports include fresh evidence such as specific code commits or deployed URLs with exact paths, correct issue linkage, and defined next actions before allowing state updates.

To verify AI reporting progress on a software feature, you need a correctly linked Linear issue, a recent progress comment, a specific verifiable artifact like a commit or URL with an exact path, and an accurately reflected project status.

No, you cannot move Linear issue states without fresh evidence. This Skill rejects progress updates that lack verifiable artifacts, defined next actions, or coherent status states, ensuring all delivery steps maintain minimum traceability.

Your AI progress report gets rejected during project status updates if it lacks verifiable artifacts with exact paths, correct issue linkage, a progress comment, defined next actions, or if the reported state is incoherent with the actual evidence.

You should apply delivery traceability checks whenever an AI is reporting progress, moving issue states, drafting or publishing comments, or affirming delivery progress within Linear and workspace folders to prevent unverified claims.