What problem does it solve? Planned work loses fidelity during implementation: vague requirements become vague tests, authors verify their own code, and long builds lose context. This Skill enforces a disciplined pipeline that extracts a provable checklist from an existing plan, builds against it, and proves every check with an independent verifier agent. ## Core Features & Use Cases - Checklist Extraction: Reads tickets, PRDs, RFCs, or threads and produces a .checks/<feature>.md artifact where every claim names a concrete proof, refuses vague requirements, and sweeps nine unwritten requirement classes like idempotency and authorization. - Profile-Based Verification: Supports light, standard, and ui profiles that add coverage joins, test-policy rows, fault injection, and design-binding screen checks depending on project configuration. - Independent Verification: Dispatches a fresh sub-agent Verifier that re-runs proofs, checks assertions against checklist values, injects behavior-level faults, and writes a verdict report. - Context Handoff: Packs whole slices into token-budgeted batches and hands off between agents using the checklist and diff rather than conversation summaries. - Use Case: A user says "implement this spec" for a billing feature; the Skill extracts checks with named proofs, builds them with Conventional Commits, and produces a verification report accounting for every check. ## Quick Start Ask the agent to implement an already-approved ticket or spec by saying "implement this spec using pbs-implement" and it will extract the checklist, build it, and verify every check.
