Replan¶
One feature is done. Before starting the next one, take a step back.
The roadmap you wrote before any code existed was a first draft. Now you've shipped a feature, you know more than you did then. Some roadmap items may be too small to deserve their own feature loop. Some may need to be reordered. Some assumptions may have changed.
Before you start the next feature, you need to replan the roadmap. It is not optional — it is what keeps the project coherent as it grows.
Start a new chat¶
Make sure you're on the main branch (you just merged). Open a new chat.
Review the roadmap¶
Read specs/roadmap.md. Look at the features still marked planned.
Ask yourself:
- Are any features too small to deserve a standalone spec → implement → test → docs cycle?
- Do any consecutive features share so much context that running them as one would be cleaner?
- Has anything you learned during Feature 1 changed the approach for a feature ahead?
For example: looking at the current roadmap, features 2 through 6 are all closely related — customer setup, rental configuration, pricing, booking, and the availability calendar all hang together. Running them as five separate features would produce five tiny spec files and five tiny commits. Combining them into one Booking & Availability feature makes the loop more meaningful.
Ask the agent to replan¶
Read specs/roadmap.md and specs/tech-design.md.
Review the remaining planned features. Identify any that are too small
to stand alone or that naturally belong together.
Propose a revised roadmap that groups related features where it makes sense.
For each new group, give it a clear name and update the "Built by" and
"Done when" columns to reflect the combined scope.
Do not merge features that have genuinely different concerns.
Do not change the status of already implemented features (done).
Present the proposed changes before writing anything.
Review the proposal. Push back if any grouping feels wrong. When you're happy, ask the agent to write the updated specs/roadmap.md.
