What problem does it solve? Verifying a feature that spans a frontend, an API layer, and a database across multiple repositories is error-prone: teams often accept mock-backed screenshots or API-only tests as proof, and environment details get hardcoded into shared workflows. This Skill enforces a disciplined six-stage contract for genuine end-to-end acceptance of vertical slices. ## Core Features & Use Cases - Six-stage acceptance workflow: Ticket, Research, Plan, Execute, Review, and Commit stages that trace a user action from browser control through hook, API, service, SQL, and back to UI readback. - Paired-environment discipline: Requires paired checkouts, independent environment leases, fixture/reset policies, and adapter-based environment configuration kept out of the public workflow. - Evidence integrity rules: Blocks acceptance when browser proof is missing, stale, or mock-backed, and mandates fresh adapter receipt checks at review time. - Use Case: A developer ships a feature touching a React UI and a backend service in separate repos; the Skill walks them through real browser actions, network expectations, and database assertions before allowing a commit. ## Quick Start Use the full-stack-slice skill to plan and verify my new profile-editing feature across the web app and API repositories with real browser and database checks.
