Cartographer

feedback-to-story-map

Map a pile of customer feedback (support tickets, NPS and CSAT comments, feature requests, app store reviews, sales call notes, churn reasons) onto a story map. Deduplicates requests into themes, finds the underlying problem behind each request, places it on the journey step where it happens, and counts which customers and segments are asking. Use when the user shares exported tickets, survey responses, a feature request list, or a CSV of feedback and wants to prioritize it, see where customers struggle, or add it to a product map or roadmap.

interview-to-story-map

Turn user interview transcripts, call recordings, or research notes into an evidence-backed story map. Writes an interview snapshot per participant, codes quotes into pains, goals, workarounds and questions, clusters them across interviews, and places each finding on the right journey step with its source. Use when the user shares an interview transcript, customer call notes, a usability test, or research findings and wants a story map, journey map, opportunity map, or wants to add the insights to an existing map.

mutual-action-plan

Build a mutual action plan (MAP), also called a mutual close plan or joint success plan: a shared timeline of every step both buyer and seller take from evaluation to signature, onboarding, go-live, and first value. Works backward from the buyer's compelling event, gives every action an owner on each side, and surfaces the paper-process risks that usually delay deals. Use when the user asks for a "mutual action plan", "close plan", "success plan", "implementation plan", "onboarding plan" for a customer, or wants to keep a late-stage deal or a new customer rollout on track.

mvp-slicing

Slice a story map or backlog into releases: a walking skeleton first, then thin, outcome-driven slices, each one a complete journey someone can use end to end. Defines the outcome and success metric for each slice, estimates it, and flags the risks to test early. Use when the user asks to "define the MVP", "slice the story map", "plan releases", "cut scope", "what's the smallest thing we can ship", build a Now/Next/Later roadmap, or fit a map into a deadline or team capacity.

sales-discovery-map

Turn sales discovery call notes or transcripts into a map of the prospect's current workflow: what their team does today, step by step, where it hurts, what that pain costs, and who is involved at each step. Adds a MEDDICC qualification check, a demo talk track that follows the prospect's own journey, and the questions for the next call. Use when the user shares discovery notes, a call transcript, an RFP, or account research and wants to qualify a deal, prep a demo, write a proposal, or brief an account team.

sales-playbook-map

Build a sales and customer success playbook on top of a customer journey map: for each step of the customer's journey, the pains to listen for, discovery questions, the value message, proof points, common objections with responses, and expansion signals, tailored per buyer role. Doubles as onboarding and training material for new reps and CSMs. Use when the user asks for a "sales playbook", "talk track", "battle card", "objection handling guide", "sales enablement", "CS playbook", or wants to train a sales team around how customers actually buy and use the product.

story-map-review

Review an existing story map or backlog for structure, balance, and hidden assumptions, then recommend the few changes that matter most. Checks the backbone reads as a story, steps are balanced, every step has a goal, risks and open questions are surfaced, releases are thin and outcome-driven, and cards are specific. Use when the user asks to "review my story map", "critique this backlog", "what's missing", "sanity check the roadmap", or shares a map before a planning session or stakeholder review.

story-map-to-backlog

Turn a story map slice into a ticket-ready backlog: user stories with a clear user, goal, and reason, acceptance criteria in Given/When/Then, rules and examples from example mapping, open questions, dependencies, and a size. Keeps each ticket linked to the journey step it came from, so the backlog still tells the story. Use when the user wants to "write the tickets", "create Jira/Linear issues from the map", "write acceptance criteria", "prepare for sprint planning", or turn a release or MVP into backlog items.

story-mapping

Guide users through story mapping, user journey mapping, and product discovery using Cartographer projects. Use when the user mentions "story map", "user journey", "journey map", "product discovery", "map the flow", "project", "user activity", "story cards", "walking skeleton", "release planning", "backlog prioritization", or wants to visualize how users interact with a product.

story-splitting

Split large user stories and epics into small, vertical, independently shippable stories using the SPIDR patterns (spike, paths, interfaces, data, rules) and the Humanizing Work splitting flow (workflow steps, CRUD operations, business rule variations, simple/complex, defer performance). Checks each result against INVEST. Use when a story is too big for a sprint, estimated L or XL, an epic needs breaking down, or the user asks "how do I split this story", "break this into smaller stories", or "this is too big".

user-story-mapping

Build a user story map from a product brief, PRD, feature idea, or conversation, following Jeff Patton's method: frame the problem, lay out the user's journey left to right as a backbone of activities and steps, fill in stories, risks and open questions, then prioritize top to bottom. Use when the user asks for a "story map", "user story map", "journey map", "backbone", "walking skeleton", wants to break a big idea into stories, or wants to see a product end to end before writing a backlog.