[!WARNING] Deprecated snapshot. Use milestone-planning for new work. This file is retained only for migration reference.

Roadmap Planning

Shape direction into outcomes that can be delivered and verified independently.

Establish the planning boundary

1. Read repository instructions, existing roadmaps or issue conventions, relevant product context, and the current request.
2. Update the existing roadmap artifact when one fits. Otherwise propose the smallest useful Markdown artifact in a repository-consistent location.
3. State the goal, constraints, current evidence, and success signals before decomposing.
4. Select the branch that matches the request:
   • for a standalone goal, shape a few independently verifiable delivery slices directly, using references/roadmap-template.md only when no local form exists;
   • for a new Milestone, prepare and score candidates before forming the task batch, then read references/milestone-planning-handoff.md before placing the confirmed result;
   • for an existing Milestone, read the same handoff reference and reconcile its delivery map.
5. Preserve precise open decisions and keep vague future questions at their current level of uncertainty.

Remain usable without a docs layout, task tracker, labels, milestone hierarchy, workflow stage, or confirmation state.