Project Roadmap

Create a roadmap from the project that exists now, not from a generic product checklist. Inspect the checkout, decide what matters, and write the result to a Markdown file.

Deliverable

• Write ROADMAP.md at the repository root unless the user names another path.
• If that file already exists, read it first. Preserve still-valid decisions and human-authored commitments; revise stale or unsupported material rather than replacing it blindly.
• Do not modify implementation code unless the user separately asks for implementation.
• In the final response, state the file written, the recommended starting point, and the evidence used to validate the roadmap.

Workflow

1. Establish the project boundary

1. Confirm the repository root and inspect git status --short --branch.
2. Preserve unrelated work and note when the checkout is dirty.
3. Inventory tracked files without descending into generated, dependency, build, or vendor directories.
4. Classify the project as a single app, library, service, multi-package repository, or monorepo.