Agile Open Sprint

When the user asks to open a new sprint for the current version. Typically also when the user asks to bump the project version, though the two are decoupled: opening a sprint is an agile-tree operation; the version bump is build-side housekeeping that you can do at the same time, before, or after.

1. Anchor the context. Find the current sprint:

   ./projects/ores.compass/compass.sh list --type sprint --sort path | tail -3
   

   The new sprint is current + 1.

2. Confirm the number with the user before scaffolding.
3. Run How do I open a new sprint? — codegen scaffold, set mission, wire into the version manifest.
4. Update the agile index — doc/agile/agile.org * At a glance table: Current Sprint → id-link to the new sprint; Next sprint → plain-text placeholder. Update #+updated:.
5. If requested, bump the project version as a separate commit/PR — How do I bump the project version?. Bumps and sprint openings are decoupled by design.
6. If requested, update the vcpkg submodule to latest as a separate commit on the same new-sprint PR — How do I update submodules to latest?. This ships the build-side housekeeping with the sprint open.
7. If the work moves to a new branch, use Feature Branch Manager. Otherwise, raise the PR via PR Manager.

• How do I open a new sprint? — the codegen + mission + manifest flow.
• How do I bump the project version? — the build-side housekeeping.
• How do I update submodules to latest? — paired build-side housekeeping for the vcpkg submodule.
• How do I create a new doc? §"New sprint" — the underlying codegen invocation.

• Sprint (glossary).
• Agile process — phases and ownership.
• Agile recipes — sibling recipes for the agile cycle.