| name | sales-userforge |
| description | Userforge platform help — an AI-assisted user-persona, user-story, and journey-mapping workspace for product and GTM teams, and the persona-cluster member that bridges a persona into a build spec: it maps user stories (User Story + Job Story formats) to personas and to the screens they touch, then exports a build-ready spec for coding agents, syncs stories to Jira as issues, and round-trips code with GitHub (Power plan). Use when generating user personas or user stories in Userforge, mapping a customer journey, exporting a persona/story spec for Claude Code or Cursor to build, syncing user stories to Jira, setting up GitHub code sync, sharing a persona via public link or inviting collaborators, comparing plan limits, or asking whether Userforge has an API (it does not — no public API/webhooks/MCP). Do NOT use for comparing persona/idea tools across the market or the validate-before-building method (use /sales-idea-validation), or building the smoke-test landing page (use /sales-funnel). |
| argument-hint | [describe what you need help with in Userforge] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","idea-validation","platform"] |
Userforge Platform Help
Userforge is an AI-assisted workspace that builds user personas, writes user stories (User
Story and Job Story formats), and lays them out on an interactive journey map — then hands the
result to a build tool as a spec (coding-agent export, Jira story sync, GitHub code round-trip). It's
the team-collaboration / build-handoff member of the persona cluster: closest to UXPressia, but
distinguished by user stories mapped to personas + screens and a spec-to-code pipeline.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer:
- What are you trying to do? (multi-select) Generate a persona · write/organize user stories ·
build a journey map · export a spec for a coding agent · sync stories to Jira · set up GitHub code
sync · share with stakeholders/invite collaborators · compare plans.
- Solo or team? (drives the plan recommendation and the collaborator/seat limits.)
- What's downstream of the persona? Building the MVP yourself (Claude Code / Cursor) · handing
stories to a dev team via Jira · just aligning stakeholders. This decides whether the spec-export /
GitHub / Jira features matter.
Skip-ahead: if the user's prompt already has enough context, go to Step 2.
Step 2 — Route or answer directly
| If the user's real question is… | Route to |
|---|
| "Which persona/idea tool should I use?" (comparing across the market) | /sales-idea-validation |
| "Does a generated persona mean people want this?" (validate demand) | /sales-idea-validation |
| "Build the smoke-test / waitlist landing page" | /sales-funnel |
| "How do I write good user stories / slice an MVP?" (tool-agnostic method) | /sales-idea-validation (persona/story method) |
| Anything Userforge-specific (features, plans, journey map, exports, Jira/GitHub sync) | Answer here with Step 3 |
When routing, give the exact command: "This is a {domain} question — run: /sales-{skill} {the user's question}"
Step 3 — Userforge platform reference
Read references/platform-guide.md for the full reference — capabilities and automation surface,
pricing/plan gates, the persona/story/journey data model, and integration recipes (Jira sync, GitHub
code round-trip, spec export for coding agents). For the exact integration/export surface (there is no
public REST API), read .
