planDefine the behavior to preserve.
Set the required behavior, file scope, and login check. Agree with your AI on what counts as done before work begins.
RECORDRequirements · Scope · Check command
GDM / VERIFIABLE WORK
Fixing a login error should also preserve the existing login flow.
Use gdm to define the criteria and check commands, then save the actual results.
gdm is a CLI for managing verification records.
Codex, Claude, and Pi skills help AI follow the process.
A RECORD YOU CAN CHECK
Set “preserve existing login behavior” as a requirement and register a login check. When work finishes, inspect the commands and results in the record.
The verification record is an illustration of the workflow.
bun test loginKeep the actual command results.
Complete the work when every required check passes.
PLAN → PASS → DONE
planSet the required behavior, file scope, and login check. Agree with your AI on what counts as done before work begins.
RECORDRequirements · Scope · Check command
passgdm executes the registered command. Review its output and exit code, and use the evidence file hash to check that the record matches.
RECORDOutput file · Exit code · SHA-256
doneRerun checks and validate the work scope and evidence integrity. Completion requires every mandatory check to pass, with results saved to the record.
RECORDAll check results · Completion status
done means verification is complete. Commit, PR, and merge permissions are handled separately.
START WITH A SKILL
Install gdm and its skills, then open a new Codex or Claude conversation in your project. gdm-go takes you from requirements through implementation and verification.
$gdm-go Fix the login error and verify the result/gdm-go Fix the login error and verify the resultCheck your CLI installation with gdm doctor. Skills require the corresponding AI tool and sign-in. AI service access is not included.