Daily Runbook

Use this every morning before implementation starts.

Morning Routine

1. Read docs/planning/active-priority.md
2. Read docs/planning/current-state.md
3. Read docs/planning/foundations-checklist.md
4. Read docs/planning/master-roadmap.md
5. Pick the next unchecked item in order
6. Confirm the owning app:
   • apps/web
   • apps/admin
7. Read the matching app spec
8. Read docs/product/domain-entities.md if the work touches business data
9. Create or update a feature spec from docs/development/feature-template.md
10. Only then start implementation

Choosing The Next Task

Use these rules:

• choose the next dependency-safe item from the roadmap
• prefer completing one coherent slice over scattering partial work
• if a task is too large for one session, split it into smaller named slices in the feature spec
• do not jump ahead to “interesting” features while the dependency chain is incomplete

During Implementation

Keep asking:

1. Does this belong in features/* or core/*?
2. Does the route name match the product?
3. Does the backend module name match the domain?
4. Do docs need updating because the plan or architecture changed?
5. Is this still in scope for the current phase?

End Of Day Closeout

Before stopping:

1. update the feature spec with what changed
2. update docs/planning/current-state.md if repo reality materially changed
3. update docs/planning/active-priority.md if the next-task stack or active phase changed
4. update docs/planning/master-roadmap.md if a roadmap item was completed or split
5. run the relevant validation commands
6. leave the next task obvious in the roadmap, active-priority doc, or feature spec

Hard Rule

Do not rely on memory for “what’s next.”

The next task must always be discoverable from:

• docs/planning/active-priority.md
• docs/planning/master-roadmap.md
• the current feature spec
• docs/planning/current-state.md