Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Agent Task State

Agents may keep temporary implementation state under spec/working/active-plans/. These files are outside mdBook navigation and are meant to be deleted after the task finishes.

Location

Use one markdown file per active task:

spec/working/active-plans/YYYY-MM-DD-task-slug.md

The active-plan files are ignored by default so stale plans do not enter history. If a plan needs to become durable documentation, move the durable parts into spec/src/ and link them from SUMMARY.md.

If the plan corresponds to a durable unimplemented item, keep the durable context in the owning package, contract, roadmap, or ADR page before treating the active plan as the source of truth.

Required Sections

Each active plan should include:

  • Goal
  • Scope
  • Current state
  • Decisions
  • Checklist
  • Blockers
  • Validation
  • Cleanup notes

Keep the file current while working. Remove completed checklist noise before promoting anything to stable docs.

Cleanup

Delete the active plan when the task is complete. The final durable state should be represented by code, tests, and stable spec pages, not a lingering task note.