tomevault-io Use When
- A queue item needs an
ExecPlan.md. - A stateless future worker must be able to resume work from the filesystem.
- Work spans multiple steps, files, blockers, or validation phases.
ExecPlan Requirements
- State the purpose, scope, non-goals, allowed paths, milestones, validation, and evidence.
- Include current facts to verify rather than unverified assumptions.
- Maintain progress, surprises, decisions, and retrospective notes as the work changes.
- Describe idempotence and recovery so a new worker can continue safely.
- Keep the plan self-contained enough that chat history is optional.
Operating Rule
Treat the ExecPlan as a living control document. Update it during execution, not only after completion. Never use it to smuggle in scope beyond the task allowlist.
Generated AIDE Source Summary
- ExecPlans are the restartable control document for long-running AIDE queue work.
- Keep Progress, discoveries, decisions, validation, recovery, evidence, and retrospective current while work runs.
- Do not use an ExecPlan to widen scope beyond the queue task allowlist.
- Generated outputs must be treated as reviewable downstream artifacts, not canonical plans.
Source: Julesc013/aide — distributed by TomeVault.