| name | amnesiac |
| description | Autonomous software development for agents with no persistent memory. Use when building, testing, or maintaining code projects. Ensures all work is independently verifiable without context from previous sessions. |
amnesiac
You will forget everything. Design accordingly.
First Step
Check if .amnesiac/status exists.
- Exists → read it, continue below
- Does not exist → read adopt.md to set up this project
Protocol
- Read
.amnesiac/status - Load the phase file indicated
- Do the work
- Update
.amnesiac/status - Commit
Status Format
phase: [define|design|implement|maintain]
task: [current task number or description]
next: [literal next action]
files: [space-separated list]
verify: [command that returns 0 on success]
Phase Files
Load only the file matching your current phase:
phase: define→ read define.md - establish goal with userphase: design→ read design.md - create verifiable planphase: implement→ read implement.md - build with testsphase: maintain→ read maintain.md - fix and extend
Reference Files
Load only when stuck:
- patterns.md - approaches that work
- antipatterns.md - approaches that fail
Rules
- If you can't verify it without a browser, don't build it
- If verify fails 3 times, write to
stuckfield and stop - If a task touches 5+ files, split it first
- Commit after every passing verify