spec-implementation-diff

Name: spec-implementation-diff
Availability: InStock
Author: burburton

Generate governance-aware diff reports between specifications and implementations.

Updated Mar 22, 2026

Search Tags:#verification #audit #compliance #governance #spec-implementation-diff

Ready to run

npx skills add https://github.com/Burburton/amazing_agent_specialist --skill spec-implementation-diff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-implementation-diff
Source: https://github.com/Burburton/amazing_agent_specialist/tree/main/.opencode/skills/reviewer/spec-implementation-diff
Command: npx skills add https://github.com/Burburton/amazing_agent_specialist --skill spec-implementation-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that implemented work remains faithful to original specifications while enforcing governance alignment across canonical documents, surfacing drift and omissions early.

Core Features & Use Cases

Surface drift between design/spec artifacts and actual implementation to support audits.
Verify governance alignment across canonical documents (role-definition.md, package-spec.md, io-contract.md, quality-gate.md, README.md).
Generate actionable diff reports to guide reviewers and inform acceptance decisions.

Quick Start

Run a diff between the spec and implementation to generate a governance-aware report.

Frequently Asked Questions about spec-implementation-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify spec compliance during code reviews?▼

Verify spec compliance by cross-checking design notes and implementation summaries against verification reports to surface drift, omissions, and scope creep. This process enforces canonical governance rules and validates canonical documents, path resolutions, and status truthfulness.

What is governance-aware spec implementation diff analysis?▼

Governance-aware spec implementation diff analysis identifies deviations between prescribed specifications and actual implementations while enforcing governance alignment. It analyzes design notes, implementation summaries, and verification reports to surface drift, omissions, and scope creep.

How do I check for specification drift before a release readiness milestone?▼

Check for specification drift before release readiness by analyzing design notes and implementation summaries against verification reports. This surfaces deviations, omissions, and scope creep while enforcing canonical governance rules including AH-006, BR-006, BR-008, and BR-009.

Can I audit canonical documents like package-spec.md and io-contract.md for governance alignment?▼

Yes, you can audit canonical documents including role-definition.md, package-spec.md, io-contract.md, quality-gate.md, and README.md for governance alignment. The analysis cross-checks these documents to verify path resolutions and status truthfulness across the implementation.

What is the best way to generate actionable diff reports for milestone validations?▼

The best way to generate actionable diff reports for milestone validations is to run a diff between prescribed specifications and actual implementations. This generates a governance-aware report guiding reviewers and informing acceptance decisions by surfacing drift early.

When should I not use automated spec implementation diffing?▼

You should avoid automated spec implementation diffing when canonical documents, design notes, implementation summaries, or verification reports are incomplete or missing. The analysis requires these inputs to accurately surface deviations, enforce governance rules, and validate path resolutions.