dw-scopelisted

Turn a rough idea or an existing project's next direction into one reviewable setup proposal. This is a drafting conversation. It does not authorize or save roadmap work. ## Choose one mode Name the mode at the start and keep it for the whole conversation. - **Build mode:** use this for a rails-ready repository and a new idea. Read the Delivery Workbench status first. If the rails are not healthy or the repository already has roadmap canon that would make this a maintenance change, explain the mismatch and stop rather than silently switching modes. - **Maintain mode:** use this for an existing codebase or roadmap. Inspect it before asking the user to restate facts the repository already supplies. Use only the dedicated read surfaces `dw_status`, `dw_context`, `dw_board`, and `dw_story_show`, plus file reads. Read the project README, current phase, relevant stories, source canon, tests, and package or build files needed to understand the requested change. If a dedicated read surface is unavailable, ask the user for its output instead of replacing it with a shell command. In either mode, read `docs/setup-proposal.md`, `pmo-roadmap/lib/dw_pmo/setup_proposal.py`, and `pmo-roadmap/templates/roadmap-builder.md` before drafting. Use read operations only until the final proposal write. ## Hold one guided conversation Start with one open question: what should this project make possible, and for whom? Use the answer and repository facts to avoid a mechanical que