codingthefuturewithai/teamcraft-jcg:define-roadmap

Goal

Produce a roadmap that answers: given everything in the PRD, what gets built in what order, over how many sprints, and why in that sequence? The roadmap is the bridge between "here are all the requirements" and "here is what we commit to this sprint." It makes sequencing decisions explicit and visible so sprint planning is selection from a ranked backlog, not improvisation.

The roadmap is an AI-native artifact — it must be structured so an agent loading it for sprint planning can immediately understand priorities, dependencies, and sequencing rationale without human interpretation.

Hard Constraints

• The roadmap organises what is already in the PRD. It does not introduce new requirements. If the user wants to add scope, direct them to update the PRD first.
• Sequencing must be grounded in reasons: dependencies between capabilities, risk reduction, walking skeleton first, client contractual milestones, technical prerequisites. Arbitrary sequencing is not a roadmap.

Load Inputs

If $ARGUMENTS contains a Confluence page URL or ID, load the PRD directly with mcp__sooperset-mcp-atlassian__confluence_get_page. Otherwise ask the user if they can point at the PRD before searching. If they need to find it, use mcp__sooperset-mcp-atlassian__confluence_search.

Ask whether a Jira project exists — if so, use mcp__sooperset-mcp-atlassian__jira_get_all_projects to identify it, then use mcp__sooperset-mcp-atlassian__jira_get_agile_boards and mcp__sooperset-mcp-atlassian__jira_get_sprints_from_board to load sprint history. Understanding what has already shipped gives the roadmap accurate starting context.

Ask whether tech decisions are available in Confluence. Load if the user can point at them — sequencing often depends on technical prerequisites.

Produce the Roadmap

Work conversationally. The PRD contains all requirements — the task is to sequence and group them into cohesive sprint-sized chunks with clear rationale.

For each roadmap item, establish: what it is (capability or feature area from the PRD), why it comes at this point in the sequence (dependency, risk, value), roughly how large it is (sprint count estimate), and what it unlocks next.

See references/example-roadmap.md for the expected structure and depth.

Surface sequencing decisions that need the user's input — when two capabilities have no dependency between them, the PM chooses priority. Do not assume.

Review and Store

Show the complete roadmap for review. Do not store until the user confirms.

Ask which Confluence space to store the roadmap in. Use mcp__sooperset-mcp-atlassian__confluence_search to surface available spaces if the user doesn't know the space key. Once the space is confirmed, use mcp__sooperset-mcp-atlassian__confluence_get_page_children to browse its structure and recommend a parent page location based on what already exists. Confirm the location before creating with mcp__sooperset-mcp-atlassian__confluence_create_page.

Done

Share the Confluence page URL and page ID. The roadmap page ID should be recorded in .teamcraft/project.md alongside the PRD and tech decisions — plan-sprint will load it as context for sprint selection. The natural next step is plan-sprint: select the first sprint's issues from the roadmap's first phase.