Research Before Executing
I'll just quickly...
continuous-improvement makes the agent research before it edits, prove every completion before it reports done, and turn each fix into an instinct it reuses next time. Seven laws run the loop; the Mulahazah engine compounds what it learns.
npx continuous-improvement install
Each law has one check to pass and one red flag to catch. The runtime keeps them automatic, so the agent reasons at a higher level instead of relying on memory.
I'll just quickly...
Let me also add...
While I'm here...
This should work...
I'll remember...
And also...
Next time I'll...
Execute moves one thing at a time. A failure never carries forward into the next task: it loops back to research.
Hooks sit between the agent and your files — they force grounding before an edit and proof before completion, acting at the boundary instead of just reminding.
Blocks Edit, Write, and destructive Bash until the agent presents a fact-list investigation. No mutating a file before naming what imports it.
A per-project ladder of checks. Nothing is marked done until the rungs pass on the actual output.
Fires a goal check when the agent tries to stop, and refuses a "Done" that has drifted from the stated goal.
Captures what worked and what failed as instincts. The same mistake does not return next session.
On the first prompt of a session it searches this project's past work and surfaces the most relevant prior fix — so the agent reuses it instead of re-deriving it. Opt-in; an amplifier, never a gate.
Install in under a minute. Two slash commands inside Claude Code, no setup.
npx continuous-improvement install