Execution Plans¶
Use this directory for work that is too large to rely on chat history alone.
docs/plans/proposals/ Feature pre-plans before implementation starts
docs/plans/active/ Plans currently being executed
docs/plans/completed/ Completed plans with final decisions and validation
Use Feature Proposals before work that changes CLI workflow shape, data or credential handling, bridge behavior, service lifecycle, release gates, or public documentation structure. A proposal decides whether the feature is worth doing, what is out of scope, and what evidence will prove it is done.
Use active execution plans after a feature is accepted and the work is large enough to need durable implementation memory. Each active plan should include:
- objective
- relevant files
- planned steps
- progress log
- validation commands
- decisions and tradeoffs
- follow-up debt
Small changes do not need a checked-in proposal or plan. Large bridge changes, persistence changes, credential handling changes, live-service workflow changes, and roadmap-changing documentation work should use one.