adaptive-mission
Installation
SKILL.md
Adaptive Mission
Core principles
- Plans are tools, not contracts: keep only the direction, 3–5 checkpoints, and each checkpoint's exit evidence. Details solidify only where requirements are stable.
- Fact sources are living: re-check the spec, acceptance criteria, interfaces, and environment facts at every checkpoint; update TRUTH.md; never carry stale assumptions from an old plan.
- State persists, plans are disposable: maintain STATE.md, TRUTH.md, REVIEW.md; PLAN.md may be thrown away and rewritten at any time.
- Doing and judging are separate: an independent Reviewer signs off after each round. Any "I think it's done" is not evidence.
- Only the real environment counts as done: simulations, dry runs, and unit tests are process evidence, not acceptance evidence.
- Stop-loss: 3 consecutive failed approaches on the same problem → stop grinding in place, switch paths or ask the user, and write a BLOCKED record.