product-prover-pack

Binds the external product-prover skill to live-spec pack paths, lenses, and review records.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/happysasha18/live-spec --skill product-prover-pack-happysasha18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-prover-pack
Source: https://github.com/happysasha18/live-spec/tree/main/skills/product-prover-pack
Command: npx skills add https://github.com/happysasha18/live-spec --skill product-prover-pack-happysasha18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the external product-prover skill runs inside a live-spec project, it needs pack-specific context it no longer carries itself: which PRODUCT_SPEC requirement codes map to which prover lenses, where the pack keeps its documents, what shape a review record must take for the push gate to accept it, and which mode names the build pipeline uses. This Skill supplies exactly those bindings so a review run inside a live-spec project stays consistent with the pack's rules. ## Core Features & Use Cases - Pin map: Maps PRODUCT_SPEC requirement codes (INV-30, INV-72, INV-244, and others) to the prover lenses that carry them, giving the pack one place to update when a lens moves or renames. - Review modes: Defines CLOSURE and GLOBAL push-review modes with fixed, pre-named scope, plus the pipeline mode names (FULL, CROSS-LINK, FEATURE-FIT, CODE-REVIEW) the prover answers to. - Record contract: Specifies the dated record shape under docs/prover/ with PUSH-REVIEW marker and required fields that guardrails/check-prover-record.sh validates before a push. - Use Case: A reviewer running the product-prover inside a live-spec repository loads this page beside the prover's own SKILL.md so findings are pinned to the right requirements and the record passes the push gate. ## Quick Start Load the product-prover-pack bindings alongside the product-prover skill and run a closure review of the accepted row before pushing this change.

Frequently Asked Questions about product-prover-pack

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

FAQPage Schema
How do I run a product-prover review inside a live-spec project?▼

Load the prover's own SKILL.md first and this pack-bindings page beside it. Every push runs a closure review of the accepted row by default, and the record is written to docs/prover/ with the PUSH-REVIEW marker before the gate script validates it.

What is the difference between closure and global review modes?▼

Closure review is the default and covers only the accepted row: its definition of done, acceptance command, diff, and touched paths. Global review runs only when the owner names a critical scope or the row changes a cross-cutting surface, and its scope is named before the read starts.

Does product-prover-pack work without the external product-prover skill?▼

No. This page only carries pack-side bindings and reviews nothing itself. It requires product-prover version 1.4.0 or higher, installed via scripts/install-external-skills.sh, which refuses versions below the minimum.

What happens when a closure review finds issues outside its scope?▼

Findings outside the review's reach become a single inbox deposit under inbox/, one paragraph per item, and the push proceeds. The deposit is judged later at the intake sweep, which decides whether a new row is owed.

When should I use code mode instead of a document review?▼

Use code mode when shipped code needs the same defect hunt a spec review runs but no document governs the surface. It applies class-based defect analysis, closed-set completeness, and sibling-defect search directly against code, with findings pinned to file:line.