teamcraft-jcg:define-roadmap

Included with Lifetime

$97 forever

Produce a multi-sprint product roadmap in Confluence — the planning layer between a baselined PRD and individual sprint planning. Organises what gets built in what order across sprints, with priorities, dependencies, and capacity rationale. Feeds directly into plan-sprint.

General

What this skill does

## 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.

Files: 2

Size: 9.0 KB

Complexity: 28/100

Category: General

Source: https://github.com/codingthefuturewithai/claude-code-primitives/tree/main/plugins/teamcraft-jcg/skills/define-roadmap

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts