evermuse

Plugin evermuse from marketplace evermuse in Usermuse/em-plugin. Commands read from the repo's manifest — 6 days ago.

Skills (45)

• analyze-feature-requests

  Triage a pile of customer feature requests into themes, merge duplicates, and surface the underlying need behind each ask — pulling the requests straight from Evermuse notes and backing every theme with quotes. Use when the user asks to 'triage feature requests', 'group these requests', 'what are cu

• assumptions

  Surface the risky assumptions behind a feature or idea, but first check the evidence — if customers already answered it, it's a finding, not an assumption — then score the rest by Impact × Risk and match each to the cheapest experiment. Use when the user asks to 'identify assumptions', 'what are we

• beachhead-segment

  Pick the first beachhead market segment by measuring which segment's people show up most and most painfully in real customer evidence, then evaluating it on burning pain, willingness to pay, winnable share, and reachability. Use when the user says 'who should we target first', 'what's our beachhead'

• brainstorm-ideas

  Generate product ideas from PM, Designer, and Engineer perspectives — seeded by the real unmet needs customers actually voiced — and return an idea→evidencing-quote mapping. Use when the user asks to 'brainstorm ideas', 'what should we build', 'come up with feature ideas', 'ideate solutions', 'what

• brainstorm-okrs

  Draft team-level OKRs — inspirational objectives with measurable key results — where each objective maps to an evidenced customer outcome and each key result measures reduction of a real, stated customer pain, aligned to company strategy via Evermuse. Use when the user wants to 'set OKRs', 'draft qu

• business-model

  Build a Business Model Canvas — all 9 blocks — with the problem and customer-segment boxes grounded in real customer evidence and the channel/competition boxes grounded in market context. Use when the user says 'business model', 'business model canvas', 'how do we make money', 'model this venture',

• competitive-battlecard

  Create a sales-ready competitive battlecard against a named competitor where the 'they say / we say' rows are ACTUAL objections and competitor mentions pulled from real customer conversations — not invented talking points. Use when the user says 'build a battlecard', 'how do we beat competitor X', '

• competitor-analysis

  Analyze competitors and find differentiation openings by cross-checking capability data against what customers ACTUALLY say about each rival — mentions, win/loss reasons, switching pain — with quotes. Use when the user says 'what do customers say about <competitor>', 'analyze our competitors', 'comp

• create-prd

  Create a business Product Requirements Document from an 8-section template — problem, objectives, segments, value propositions, solution, release — grounded in real customer evidence (verbatim quotes, needs, pains with source links) from Evermuse. Use when the user wants to 'write a PRD', 'create a

• customer-journey-map

  Map the end-to-end customer journey — awareness through advocacy — with the real pain point, emotion, and a verbatim customer quote at each stage, plus prioritized fixes. Use when the user says 'map the customer journey', 'map the user journey', 'where do users drop off', 'improve onboarding', 'what

• customer-research

  Answer questions about what customers actually think, need, ask for, or complain about — by searching real customer evidence in Evermuse and returning a quote-rich, source-linked brief. Use when the user asks 'what do customers think about X', 'have customers asked for Y', 'what are the biggest pain

• daily-brief

  Write and deliver the recurring Evermuse daily brief — everything Evermuse learned from customer sources in the last 24 hours, quoting customers only and never the internal team. Use when the scheduled daily report task fires, when the user runs find_skills:daily-brief, or asks 'send my daily brief'

• deep-dive

  Dive deep into one topic the user cares about — first ask what's top-of-mind, then answer it with a quote-rich, source-linked brief grounded in real customer evidence from the Evermuse Mock Data corpus. Use when the user picks "Dive into a topic", runs find_skills:deep-dive, or says 'let's go deep o

• development-plan

  Create a development plan for a feature that starts from what customers actually requested — Evermuse quotes and demand evidence carried into the plan itself — then applies spec-driven phasing and a dependency-ordered task list. Use when the user says 'plan this feature', 'create a dev plan', 'how s

• gap-analysis

  Audit an existing spec, plan, or shipped feature for gaps across three lenses — spec-vs-spec consistency, spec-vs-code implementation, and whether the build covers what customers need — with every finding backed by evidence. Use when the user asks to 'do a gap analysis', 'what's missing from the spe

• gtm-strategy

  Build a go-to-market strategy — messaging, channels, segment focus, GTM motions, metrics, and a launch timeline — where every choice is anchored in real customer evidence, not guesswork. Use when the user says 'plan the launch', 'build a GTM plan', 'how do we take this to market', 'what channels sho

• ideal-customer-profile

  Build an Ideal Customer Profile from your real won-and-happy customers — firmographics, behaviors, jobs-to-be-done, and pains drawn from actual conversations with the accounts that bought and stayed. Use when the user says 'define our ICP', 'who is our ideal customer', 'who are our best customers',

• initial-report

  Present the first Evermuse report after the initial source scan - Use right after ingestion completes, when the user picks "Get my initial report", runs find_skills:initial-report, or asks 'show me my initial report', 'what did you learn from my sources', 'give me the first report', or 'what pattern

• interview-script

  Write a Mom-Test customer interview guide — warm-up, JTBD exploration, wrap-up — but first check the evidence for what's ALREADY known so the questions target the open gaps instead of re-asking answered questions. Use when the user asks to 'write an interview script', 'prep for a user interview', 'd

• list-capabilities

  Show the user everything Evermuse can do — announce it in chat, then render the interactive list-capabilities picker of every agentic skill, grouped by category, and wait for them to pick one. Use when the user picks "See all new capabilities", runs find_skills:list-capabilities, or asks 'what can y

• market-sizing

  Estimate market size (TAM, SAM, SOM) with top-down and bottom-up approaches, grounded in market/industry signals and validated against a real customer beachhead. Use when the user says 'how big is the market', 'what's our TAM', 'size this opportunity', 'estimate the addressable market', 'prep market

• north-star-metric

  Define a customer-centric North Star Metric plus a tree of 3-5 input metrics that drive it, where the North Star is anchored to the actual value customers describe getting from the product in real evidence. Use when the user says 'define our north star', 'what should we measure', 'pick a key metric'

• opportunity-solution-tree

  Build a Teresa Torres Opportunity Solution Tree — outcome → opportunities → solutions → experiments — where every opportunity node is backed by a real customer quote and unsupported nodes are flagged as unproven hypotheses. Use when the user asks to 'build an opportunity solution tree', 'map opportu

• outcome-roadmap

  Transform a feature-list (output) roadmap into an outcome-focused one — each lane rewritten as 'Enable [segment] to [outcome] so that [business impact]' and citing the demand evidence behind it, grounded in Evermuse. Use when the user wants to 'make the roadmap outcome-focused', 'rewrite the roadmap

• positioning-and-messaging

  Generate differentiated positioning options and campaign/message ideas written in your customers' own mined vocabulary, where every message maps to a real quote that proves it resonates. Use when the user says 'how should we position this', 'position the product', 'differentiate from competitors', '

• pricing-strategy

  Design pricing and monetization grounded in real willingness-to-pay signals, pricing objections, and value language from customer evidence — with competitor pricing as a labeled secondary input. Use when the user says 'how should we price this', 'pricing strategy', 'what should we charge', 'pricing

• prioritize-features

  Rank a backlog of feature ideas using real demand counts from customer evidence — Reach and Impact come from how many distinct accounts actually asked, not a gut number — and return a top-5 with the quotes behind each score. Use when the user asks to 'prioritize features', 'what should we build next

• product-strategy

  Build a product strategy on the 9-section Product Strategy Canvas where every pillar is anchored in real customer evidence and market context, not guesswork. Use when the user says 'build a product strategy', 'what's our strategy', 'define our product direction', 'strategic plan', 'how do we win', o

• product-vision

  Craft an inspiring, achievable product vision anchored in customers' own words about the future they want — not internal aspiration alone. Use when the user says 'write a product vision', 'vision statement', 'what's our north star', 'align the team on direction', 'where are we headed', or 'refine ou

• release-notes

  Generate user-facing release notes / changelogs from tickets, PRDs, or git logs — organized by new features, improvements, fixes — with a 'You asked, we built' angle that finds the real customers who requested each shipped item via Evermuse. Use when the user wants to 'write release notes', 'create

• review-pr

  Review a pull request against three things at once: code quality, the spec it was meant to satisfy, and the actual customer asks behind it — calling out where the diff diverges from what customers literally requested. Use when the user asks to 'review this PR', 'review the diff', 'check this PR agai

• schedule-new-ingestion-tasks

  Add future-facing Evermuse ingestion tasks for newly connected customer-feedback sources in Claude or ChatGPT. Use after setup-evermuse when the user wants to schedule additional sources; never backfill historical records or recreate tasks for sources already covered. - evermuse - ingestion - schedu

• segmentation

  Segment a market or user base by evidence-based need differences — not demographics — into 3-5 distinct groups, each with its jobs-to-be-done, pains, product fit, and representative customer quotes. Use when the user says 'segment our users', 'segment the market', 'who are our target segments', 'wha

• sentiment-analysis

  Analyze the feedback corpus over a time period to surface sentiment, themes, and satisfaction shifts — with a score per theme and verbatim quotes carrying their own sentiment labels. Use when the user says 'how do users feel about X', 'what's the sentiment on Y', 'analyze feedback from last quarter'

• setup-evermuse

  This skill sets up the Evermuse MCP extension prototype inside your agentic app. It will guide you through the setup process, asking key questions along the way using our UI rendering tools and skills. - install - product - customer voice

• shipping-artifacts

  Generate the ship-readiness documentation set for an AI-built (vibe-coded) feature — architecture, flows, permissions, variables, and a tests coverage map, plus conditional docs — and reconstruct the missing 'intent' section from Evermuse shaping notes, the local spec, and customer evidence so a rev

• strategy-frameworks

  Run a classic strategy framework — SWOT, PESTLE, Porter's Five Forces, or Ansoff Matrix — where every cell cites a real customer-evidence or market-context result instead of generic filler. Use when the user says 'do a SWOT', 'PESTLE analysis', 'Porter's five forces', 'Ansoff matrix', 'strategic ass

• strategy-red-team

  Adversarially attack a strategy, PRD, or roadmap by hunting the customer counter-evidence that falsifies its claims — 'you assume X, but three customers said the opposite'. Includes a pre-mortem mode. Use when the user says 'red-team this', 'poke holes in this', 'stress-test our strategy', 'pressure

• summarize-conversation

  Summarize one customer interview or team meeting into structured notes — participants, needs/JTBD, verbatim quotes with timestamps, decisions, action items — by locating the conversation in Evermuse and reading its transcript. Use when the user says 'summarize this interview', 'summarize the meeting

• test-scenarios

  Create QA test scenarios in Given/When/Then form from a spec's acceptance criteria AND from the real edge cases customers actually hit — failure stories and complaints pulled from Evermuse so the test plan covers reality, not just the happy path. Use when the user wants to 'write test scenarios', 'c

• user-personas

  Build user personas from the real people in a company's customer corpus — 3 evidence-backed personas with jobs-to-be-done, pains, gains, and an 'in their own words' verbatim quote block each. Use when the user says 'build personas', 'create user personas', 'who are our users', 'make a persona for X'

• user-stories

  Break a feature into user stories (or job stories) — INVEST-shaped, 3-C's structure, each story citing the motivating customer quote and acceptance criteria that reflect what customers actually expect, grounded in Evermuse evidence. Use when the user wants to 'write user stories', 'break this into s

• using-evermuse

  Foundational doctrine and mechanics for grounding product work in real customer evidence via the Evermuse MCP — loaded by every other Evermuse skill. Use when you need the shared rules for how to search Evermuse, cite customer quotes with source links, resolve the active Product/Project, or save del

• value-proposition

  Design a value proposition on the 6-part JTBD structure, then turn it into ready-to-use marketing/sales/onboarding statements — all in customers' verbatim language. Use when the user says 'write our value proposition', 'value prop', 'why should customers choose us', 'positioning statement', or 'arti

• write-feature-spec

  Write a feature specification grounded in real customer evidence — verbatim quotes, needs, and pain points with source links from Evermuse — using spec-driven-development structure (prioritized user stories, Given/When/Then acceptance scenarios, functional requirements, measurable success criteria).

Slash commands (34)

• /evermuse:analyze-feedback

  Run sentiment and theme analysis over a period of customer feedback, with quotes carrying real sentiment signals

• /evermuse:battlecard

  Create a sales battlecard whose objection-handling rows are real customer objections and competitor mentions from the corpus

• /evermuse:brainstorm

  Brainstorm feature or product ideas seeded by real unmet customer needs, from PM, designer, and engineer perspectives, each idea mapped to the evidence behind it

• /evermuse:business-model

  Explore a business model with evidence-backed problem and segment assumptions — Business Model Canvas, Lean Canvas, or Startup Canvas

• /evermuse:competitive-analysis

  Analyze the competitive landscape, cross-checking competitor capabilities against what customers actually say about rivals in real conversations

• /evermuse:dev-plan

  Create a development plan that starts from what customers actually requested — quotes and demand evidence in the plan, plus spec-driven phasing and a dependency-ordered task list

• /evermuse:discover

  Run a discovery cycle grounded in customer evidence — map an opportunity-solution tree from real needs, then surface and prioritize the riskiest assumptions

• /evermuse:gap-analysis

  Find gaps across three lenses — spec-vs-spec consistency, spec-vs-code implementation, and spec-vs-customer demand coverage — each finding backed by evidence

• /evermuse:growth-strategy

  Design a growth strategy — define a customer-value-grounded North Star and the GTM motions to move it

• /evermuse:interview

  Prepare a Mom-Test interview script targeting what evidence cannot yet answer, or summarize an interview transcript into needs, quotes, and action items

• /evermuse:market-product

  Generate positioning options and campaign ideas written in mined customer vocabulary, each message mapped to a quote that proves it resonates

• /evermuse:market-scan

  Run a market or environment analysis (SWOT, PESTLE, Porters Five Forces, or Ansoff) where each cell cites a real evidence or market-context result

• /evermuse:meeting-notes

  Summarize a customer meeting or interview transcript into decisions, needs, verbatim quotes, and action items

• /evermuse:north-star

  Define a North Star Metric and its input-metric tree, tied to the customer value evidenced in real conversations

• /evermuse:plan-launch

  Plan a go-to-market: pick a beachhead by demand density, profile the ideal customer, and build the GTM strategy — all grounded in customer evidence

• /evermuse:plan-okrs

  Brainstorm team OKRs whose objectives map to evidenced customer outcomes and whose key results measure real pain reduction

• /evermuse:pre-mortem

  Run a pre-mortem on a strategy, PRD, or roadmap — imagine it failed and trace why, citing counter-evidence where customers already signal risk

• /evermuse:pricing

  Design a pricing and packaging strategy grounded in willingness-to-pay signals, pricing objections, and value language from real customer conversations

• /evermuse:red-team-prd

  Adversarially stress-test a PRD, roadmap, or strategy by attacking its load-bearing assumptions with customer counter-evidence

• /evermuse:release-notes

  Write "you asked, we built" release notes — for each shipped item, surface the customers who requested it (quoted internally, counted externally) and flag follow-ups

• /evermuse:research-users

  Build evidence-based personas and segments from real people and conversations in the corpus

• /evermuse:research

  Answer a question about what customers think, need, ask for, or complain about — a quote-rich, source-linked brief drawn from real customer conversations in Evermuse

• /evermuse:review-pr

  Review a PR against code quality, the spec it should satisfy, and the actual customer asks behind it — flagging where the diff diverges from what customers requested

• /evermuse:save

  Save the current research, spec, plan, or analysis back into Evermuse so the knowledge base compounds

• /evermuse:setup

  Connect and verify Evermuse — confirm the MCP is authorized, pick the right Product (and Project if needed), and run a smoke-test search

• /evermuse:ship-check

  Turn a built feature into a reviewer-ready packet — generate shipping artifacts, then run a customer-grounded gap analysis

• /evermuse:spec

  Write a feature specification grounded in real customer evidence — prioritized user stories, acceptance scenarios, and requirements with verbatim customer quotes and source links

• /evermuse:strategy

  Build a product strategy where every pillar is grounded in customer pains (evidence) and market shifts (context), aligned to stated company objectives

• /evermuse:test-scenarios

  Generate Given/When/Then test scenarios from a spec plus the edge cases customers actually hit in real conversations

• /evermuse:transform-roadmap

  Transform a feature-based roadmap into an outcome-focused one where each outcome lane cites the customer demand behind it

• /evermuse:triage-requests

  Triage a batch of customer feature requests into themes, duplicates, and the underlying needs behind them, prioritized by real demand

• /evermuse:value-proposition

  Design a value proposition in the customers own words — pains and gains pulled verbatim from real conversations — plus ready-to-use value-prop statements

• /evermuse:write-prd

  Create a business PRD (8-section) grounded in customer evidence — the lighter sibling of a full spec-driven feature spec

• /evermuse:write-stories

  Break a feature into user stories or job stories, each citing the customer quote that motivated it and acceptance criteria reflecting stated expectations

MCP servers (1)

• evermuse

  connects to: https://api.evermuse.com/api/mcp

Similar plugins