derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage…
Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan
> /plugin marketplace add phuryn/pm-skillsHow it fires
How this command gets triggered: by you, by Claude, or both.
/plan-launchContext preview
What this command does when you run it.
Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan
description: Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan argument-hint: "<product or feature to launch>"
Build a complete GTM plan from first principles: identify your beachhead market, define the ideal customer, craft messaging, choose channels, and create a launch timeline.
/plan-launch AI-powered proposal writer for consulting firms /plan-launch New enterprise tier for our project management tool /plan-launch [upload a PRD, strategy doc, or pitch deck]
Ask:
Apply the **beachhead-segment** skill:
Apply the **ideal-customer-profile** skill:
Apply the **gtm-strategy** skill:
## Go-to-Market Plan: [Product/Feature] **Launch date**: [target] **Type**: [new product / feature / tier / market expansion] ### Beachhead Segment **Who**: [specific segment definition] **Why them first**: [rationale against criteria] **Size**: [TAM/SAM/SOM estimate] ### Ideal Customer Profile | Attribute | Definition | |-----------|-----------| | Company size | [range] | | Industry | [specific] | | Decision maker | [title/role] | | Key JTBD | [job they need done] | | Current solution | [what they use today] | | Qualification signal | [how to identify them] | ### Positioning & Messaging **Positioning statement**: For [who] who [need], [product] is [category] that [benefit]. Unlike [alternative], we [differentiator]. **Key messages by stakeholder**: | Audience | Message | Proof Point | |----------|---------|------------| ### Channel Strategy | Channel | Tactic | Reach | Cost | Priority | |---------|--------|-------|------|----------| ### Launch Timeline | Phase | Timing | Actions | Owner | |-------|--------|---------|-------| | Pre-launch | [dates] | [list] | [who] | | Launch week | [dates] | [list] | [who] | | Post-launch | [dates] | [list] | [who] | ### Success Metrics | Metric | 30-day target | 90-day target | |--------|-------------|-------------| ### Risks & Mitigations | Risk | Likelihood | Impact | Mitigation | |------|-----------|--------|-----------| ### Expansion Plan [After beachhead: which adjacent segments, in what order, with what adaptations]
Save as markdown.
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage…
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus…
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by…
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed…
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage,…
Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends