Always Work From A Plan
Work that survives the session, or grows out of its scope, gets a written plan. For product features, the plan is step 1 of the Feature Workflow.
Why
A plan in a file lets any other session or agent continue from where the previous one stopped.
How To Apply
Where The Plan Lives
- In a project, all work follows the project's workflow.
- Read the workflow before starting any project work, every session.
- Outside a project, the plan is a file of its own.
Working From The Plan
- Work from the plan, even one you wrote.
- Read it before starting and update it as you go.
- A plan holds what was asked and decided. A doubt goes to the director, never into the plan as a gate.
- It shrinks toward empty per Plans Vs Persistent Files.
- Plans are documentation. Follow the same markdown conventions as persistent docs (see Documentation Philosophy), even though plans are temporary.