Failing test first
The contract fails before production code changes.
STATE 00REQUEST
A method for engineering agents that does not trust claims.
galdr routes each request, requires a failing test before production code, and records fresh evidence before work is called done.
EXECUTION / 01DETERMINISTIC
- 01REQUESTAdd a customer report export.Received
- 02ROUTEshape-synthesisSelected
- 03REDThe focused page contract fails.Expected stop
- 04GREENThe focused page contract passes.Verified
- 05GATETests, build, lint, and types pass.Verified
- 06RECORDEDCommand, verdict, and commit are kept.Complete
Sequence complete
STATE 01METHOD
The connected method
route → shape → plan → waves → verify → memory
- 01Orient
Route
Match the request to the smallest useful workflow.
OUTPUTA clear starting point - 02Frame
Shape
Turn an uncertain idea into a decision-ready brief.
OUTPUTA bounded problem - 03Commit
Plan
Make the work executable before changing the system.
OUTPUTA tested path - 04Build
Waves
Deliver independent slices with visible evidence.
OUTPUTWorking increments - 05Prove
Verify
Check the outcome against the promise and the code.
OUTPUTProof of completion - 06Learn
Memory
Keep the decisions that make the next request sharper.
OUTPUTDurable context
Root cause before a fix
Reproduce and isolate the cause before changing behavior.
Fresh evidence before done
Run the proving command again after the last code change.
STATE 02ROUTE
The request sets the workflow
Four repository-backed examples. One deterministic next move for each.
Route lab
Choose the next engineering move
- Route
- debug
- Reason
- A failure needs evidence before a fix.
- Next action
- Reproduce, isolate, and verify the cause.
- Route
- shape-synthesis
- Reason
- The desired outcome needs a useful boundary.
- Next action
- Shape the workflow before implementation.
- Route
- rearchitect
- Reason
- The system structure is now the constraint.
- Next action
- Map the deployment and ownership seams.
- Route
- answer
- Reason
- The information is already available.
- Next action
- Answer directly and cite the source of truth.
STATE 03GATE
Proof, not claims
galdr keeps concrete outputs that another engineer can inspect and rerun.
Evidence gates
A gate records the command, verdict, key numbers, and commit before a completion claim can pass.
Durable memory
Decisions and evidence remain available to the next request instead of living only in one chat.
Crash recovery
A continuation reads the brief, current progress, and live repository state before work resumes.
Independent review
A reviewer inspects the diff and reruns the gate. Another agent's report is never accepted as proof.
SAMPLE EV [3.1 RED] npx vitest run tests/page-contract.test.ts → FAIL (expected page contract)
SAMPLE EV [3.1 GREEN] npx vitest run tests/page-contract.test.ts → PASS 10 passed 0 skipped
STATE 04INSTALL
Install galdr
Choose the agent runtime, copy the public install command, then enable core routing when you want it.
Install galdr
/plugin marketplace add nyelonong/galdr /plugin install galdr@nyelonong
Enable core
/galdr:core install claude
Install galdr
npx skills add nyelonong/galdr
Enable core
/galdr:core install codex
Install galdr
npx skills add nyelonong/galdr
Enable core
/galdr:core install antigravity
Need the complete package? Open the public repository or read the full documentation.