Connect

Spec vs. Shipped

Sidsaladi9bySidsaladi9
•
6
•
Collaboration Tools

Audits shipped features against product specifications to detect delivery drift and turn gaps into actionable decisions.

Spec vs. Shipped systematically reconciles what was promised in a product specification or PRD against what actually made it into production via pull requests, tickets, and live software. Grounded in modern product management and blameless postmortem methodologies, this skill extracts requirements, compares them against delivered artifacts, and isolates deliberate team decisions from unmonitored scope drift. It ensures teams catch unpriced risks, audit unspecced additions, confirm whether releases can still achieve target metrics, and update documentation before publishing release notes or running milestone retrospectives.

Key Features

016 GitHub stars
02Line-by-line reconciliation of PRD acceptance criteria against shipped PRs and live product behavior
03Decided vs. drifted classification to isolate intentional trade-offs from silent scope drops
04Detection and risk auditing for unspecced additions that add unpriced maintenance burden
05Metric impact evaluation to confirm whether missing items compromise target business outcomes
06Definitive decision matrices assigning clear resolution actions and owners for every identified gap

Use Cases

01Pre-launch verification before publishing release notes, marketing copy, or customer announcements
02Milestone delivery retrospectives to anchor discussions on objective facts rather than speculation
03Inheriting legacy or adrift projects to restore accurate documentation against current product behavior