superpm

/superpm - one PM request, a verified artifact

One PM ask -> capture intent -> diverge by domain -> the smallest useful artifact -> an independent critic checks it against the framework and the real decision -> stop.

68 PM frameworks live in reference/; this file routes the ask and names the loop. For a one-paragraph note you could write directly, skip the skill.

Principles

Serve the real decision. Name the decision the artifact drives before drafting; a framework filled in for its own sake is waste.
Smallest useful artifact. Only the frameworks the decision needs - no bolted-on SWOT/persona/roadmap when the ask was one pricing call.
Ground claims in evidence. Numbers, quotes, segments come from the user's data, docs, or named assumptions - never invented.
Surface hidden assumptions. The critic names unstated assumptions and missing pieces as risks - never present an assumption as fact.
Ask only when genuinely ambiguous. Read the repo/docs/data first; interview only load-bearing, user-only choices (reference/intent.md).
Hard stops. Irreversible or outward-facing actions (publish, send, post, share externally) need explicit consent.
Trace the chain. EXECUTE -> FLOW -> STORYBOARD -> PACKAGE share the feature specification (SPEC) as one source of truth (reference/model.md); a flow node or screen callout with no SPEC is never invented. Derived artifacts come from the spec, not beside it.

Intent capture - signal to domain

Read the request and route to one domain (the artifact named usually decides it). When the ask spans domains, pick the primary deliverable and pull supporting frameworks from the others. When the ask is to plan a buildable thing end-to-end (plan it / I want to develop this, no single artifact named), route to PLAN - a stepped session over the chain, not one artifact (reference/plan.md).

Signal in the request	Domain	Reference
plan it / I want to develop this / help me plan / plan this feature end-to-end / from PRD to screens	PLAN (session)	`reference/plan.md`
brainstorm ideas / risky assumptions / opportunity tree / prioritize features / customer interview / metrics	DISCOVER	`reference/discover.md`
product strategy / vision / value proposition / lean or business model / monetization / pricing / SWOT / PESTLE / Porter / Ansoff	STRATEGY	`reference/strategy.md`
PRD / OKRs / roadmap / sprint plan / retro / pre-mortem / user or job stories / stakeholder map / prioritization framework / red-team a plan	EXECUTE	`reference/execute.md`
user flow / user flow / flowchart / screen-to-screen flow / screen flow / branching and state transitions	FLOW	`reference/flow.md`
screen design document / feature specification / storyboard / screen design doc / screen spec / wireframe / UI spec	STORYBOARD	`reference/storyboard.md`
implementation package / implementation package / integrated deliverable bundle / export bundle / hand off to devs	PACKAGE	`reference/package.md`
personas / segments / customer journey / market sizing (TAM/SAM/SOM) / competitor analysis / sentiment	RESEARCH	`reference/research.md`
SQL from a question / cohort analysis / A/B test read-out	ANALYTICS	`reference/analytics.md`
go-to-market / beachhead / ICP / growth loops / GTM motion / battlecard	GTM	`reference/gtm.md`
marketing ideas / positioning / value-prop statements / product name / North Star metric	GROWTH	`reference/growth.md`
review or tailor a resume / draft an NDA or privacy policy / proofread	TOOLKIT	`reference/toolkit.md`
document an AI-built app / shipping artifacts / intended-vs-implemented gap	AI-SHIP	`reference/ai-ship.md`

The domain decides which reference loads; the loop is the same for all. Cross-cutting: asks about what the market/customers want (demand, trends, voice of customer) ground the artifact in reference/signal.md first.

The loop - Capture, Frame, Draft, Critic, Deliver

Capture. Classify and record one line - Domain: <X> | Artifact: <Y> | Decision it serves: <Z> - even when nothing is ambiguous. If genuinely underspecified, run the reference/intent.md gate (<=5 questions, one batched round, a recommended answer per question). Resolve doc/data-answerable questions by reading, not asking.
Frame. Extend that line into the artifact's ## Intent block: classification, the real decision, and the completion bar (what "done and trustworthy" looks like for this framework). This block is the contract the critic checks against.
Draft. Load reference/<domain>.md and apply the named framework. Use the user's real inputs; mark gaps as explicit assumptions. Smallest useful artifact - no filler frameworks.
Critic (independent). Run reference/critic.md. Independence is mechanical: if the harness supports subagents, hand a fresh one only the ## Intent block + the draft; otherwise switch stance and read cold. Red-team all four checks: missing framework sections, unsupported claims, dodged decisions, unvalidated assumptions - each emitted as a risk. Do not self-congratulate a draft to green.
Deliver. Fold blockers and gaps back in; leave user-owned risks in a ## Critic block. Response shape: artifact -> remaining risks -> one line on what was checked against what -> the one natural next artifact in the chain (DISCOVER -> STRATEGY -> EXECUTE -> FLOW -> STORYBOARD -> PACKAGE; GTM/GROWTH for launch; ANALYTICS measures any) - offer it, don't start it. Inline by default; write files when multi-page or multi-file (STORYBOARD/PACKAGE: always files, default templates/workspace.html - the interactive SSOT canvas) and report paths. Outward/irreversible steps wait for explicit consent.

For a PLAN session (reference/plan.md), run this loop once per stage (EXECUTE -> FLOW -> STORYBOARD -> PACKAGE), gating for the user after each and carrying the running SSOT JSON forward; the whole chain is the deliverable, ending in workspace.html + a PACKAGE.

Follow-up turns

The loop is per-artifact, not per-message. On iteration:

Substantive change (new claim, section, or decision) -> re-Draft, re-run the critic on the delta only.
Tone / format / length-only edits -> no critic re-run.
New artifact or new domain -> new loop from Capture. "Another idea / different one" in DISCOVER follows the idea-proposal batch rule (reference/discover.md).
Keep the loaded domain reference; do not re-read it each turn.

Reference map

Read	When
`reference/intent.md`	Capture: ambiguity-gated <=5 question interview before drafting
`reference/critic.md`	Critic: independent red-team verification gate (every domain)
`reference/signal.md`	Signal: live market & customer evidence (voice of customer), read-only + keyless; feeds RESEARCH/DISCOVER/GTM, delegates to the `last30days` skill if present
`reference/model.md`	MODEL: shared data contract (SSOT) - identifiers, entities, sync rules R1-R6, validation codes; flow/storyboard/package/critic reference it (cross-cutting)
`reference/plan.md`	PLAN: stepped build-planning session - EXECUTE→FLOW→STORYBOARD→PACKAGE over one SSOT, gated per stage (orchestrator)
`reference/discover.md`	DISCOVER: ideation, assumptions, OST, prioritization, interviews, metrics
`reference/strategy.md`	STRATEGY: strategy canvas, vision, value prop, lean/business model, pricing, analysis frameworks
`reference/execute.md`	EXECUTE: PRD, OKRs, roadmap, sprint, retro, pre-mortem, stories, stakeholder map, prioritization
`reference/flow.md`	FLOW: user-flow graph - nodes derived from SPECs (R2), page->screen hand-off (R3), zero-dep visualization (text step list + `templates/workspace.html` FLOW SVG canvas)
`reference/storyboard.md`	STORYBOARD: screen design document/feature specification - derive screens, per-element spec; default output `templates/workspace.html` (interactive 3-tab SSOT canvas: feature specification/user flow/wireframe); per-screen image-replica set (Mode A) optional via bundled HTML / `storyboard-spec`
`reference/package.md`	PACKAGE: integrated implementation bundle - one snapshotId over PRD+spec+flow+wireframe (R6), back-link integrity, md/json/svg/html export
`reference/research.md`	RESEARCH: personas, segments, journey map, market sizing, competitor, sentiment
`reference/analytics.md`	ANALYTICS: NL->SQL, cohort, A/B test
`reference/gtm.md`	GTM: strategy, beachhead, ICP, growth loops, motions, battlecard
`reference/growth.md`	GROWTH: marketing ideas, positioning, value-prop statements, naming, North Star
`reference/toolkit.md`	TOOLKIT: resume, NDA, privacy policy, proofread
`reference/ai-ship.md`	AI-SHIP: shipping artifacts, intended-vs-implemented
`templates/`	Reusable artifact scaffolds (PRD, strategy canvas, OST, battlecard, storyboard page/board, workspace 3-tab, ...)

Output language

Write the artifact in the user's language. Keep framework names, metric names, and machine-checked anchors (SQL, identifiers, file paths) in their canonical form.