What problem does it solve? AI-assisted development often ends with unverified claims like "the code looks correct," leading to broken builds, failed endpoints, and UI regressions discovered only later. This Skill enforces proof-based completion so no task is marked done without observable evidence. ## Core Features & Use Cases - Validation Methods by Change Type: Maps each change type (UI, API, build/config, data, file operations) to a required verification tool such as browser screenshots or command output. - Four-Step Validation Protocol: Identify verification criteria, execute verification, document evidence in .gsd/JOURNAL.md, and confirm results against expectations. - Failure Handling Workflow: Failed verifications block task completion, get documented in .gsd/STATE.md, generate fix tasks, and trigger the Context Health Monitor after 3+ failures. - Use Case: After modifying a login API endpoint, run a curl request against it, capture the actual JSON response showing a success token, and record that output in the journal before closing the task. ## Quick Start Ask the AI to verify the most recent change using the empirical validation protocol and record the evidence in the GSD journal.
