Execution plans are Git-native working memory for complex tasks. They preserve enough context for another agent or human to resume work without reconstructing intent from chat history or a partial diff.

Use an ephemeral plan for bounded, single-session work.

Create one durable plan when work spans sessions, coordinates contributors, has meaningful dependencies or ordering, requires recovery steps, or would be unsafe to resume from the diff alone.

Use docs/templates/exec-plan.md and place the file under active/.

docs/plans/active/<slug>.md
  -> update progress and decisions during implementation
  -> record final validation and result
  -> move to docs/plans/completed/<slug>.md

The plan is the primary task artifact. Promote a lasting product or architecture decision into docs/decisions/; keep task-local choices in the plan.

Do not merge completed plans that record different migrations. Cross-link them. Rename an active plan when its ADR number or workstream id changed.

• 2026-09-28-mstest-host-provider.md — MSTest 4.4.1 host provider (0038)
• 2026-09-04-mcp-test-project-split.md — MCP test project split