Files

1.3 KiB

exec-plans Index

Purpose

Execution plans for multi-step work that spans multiple PRs or sessions. These plans are durable coordination artifacts for agents, not temporary notes. Active work lives in active/; shipped work is archived to completed/; debt that is known but unscheduled stays in the tracker.

File conventions

  • Each plan is a Markdown file with sections: Goal, Steps, Dependencies, Validation.
  • Name plans by workstream and date (e.g., websocket-refactor-2026-04.md).
  • Move plans to completed/ when all steps are done and shipped.
  • Record meaningful design decisions in the plan instead of assuming chat context will survive.

Files

Subdirectories