survival-check

To validate that plan tasks survive context compaction, run a survival check on your PLAN.md to split it into per-task blocks and verify each block is self-contained. It generates a .survival-check.md file with PASS/FAIL verdicts to gate execution.

A self-contained plan block is a task segment that operates independently after context compaction by using explicit file references, context pointers, and contracts instead of relying on prior conversation history or hidden state.

You can review PLAN.md files for hidden context dependencies by running a survival check gate that flags task blocks relying on previous conversation or implicit state, emitting a .survival-check.md artifact with an overall PASS or FAIL gating decision.

Yes, you can use survival-check for plan-validation when tasks reference prior outputs. It enforces explicit file references and context pointers within each PLAN.md task block to ensure they remain self-contained during context compaction.

Plans break mid-execution after a context shift because task blocks lack explicit file references and context pointers, causing them to fail when prior conversation history or hidden state is compacted. A survival check gate prevents this by validating self-containment beforehand.

No external dependencies are required to perform a plan-review survival check. The tool independently splits PLAN.md into per-task blocks, validates their self-containment, and emits the .survival-check.md artifact with per-task verdicts.