gtm-motions▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Identify and evaluate the best go-to-market motions for your product. This skill analyzes seven proven GTM approaches with specific tools and tactics to help you build a balanced acquisition strategy.
GTM Motions
Overview
Identify and evaluate the best go-to-market motions for your product. This skill analyzes seven proven GTM approaches with specific tools and tactics to help you build a balanced acquisition strategy.
When to Use
- Selecting marketing channels for your product
- Choosing between inbound vs outbound strategy
- Building your GTM toolkit and tech stack
- Evaluating PLG vs traditional sales motion
- Planning cross-channel marketing campaigns
The 7 GTM Motions
1. Inbound Marketing
Attract customers through valuable content and thought leadership.
- Tools: LinkedIn, SEMRush, Grammarly, HubSpot, Airtable
- Tactics: Blog content, webinars, whitepapers, SEO, email nurture sequences
- Best For: B2B SaaS, technical products, long sales cycles
- Strength: Builds brand authority and attracts high-intent prospects
- Challenge: Requires consistent content creation; slower to show results
2. Outbound Sales
Proactively reach target prospects through direct engagement.
- Tools: LinkedIn Sales Navigator, ZoomInfo, Lemlist, Apollo, Hunter
- Tactics: Cold email campaigns, LinkedIn outreach, phone prospecting, personalized demos
- Best For: Enterprise sales, high-value contracts, niche markets
- Strength: Predictable pipeline generation; control over target selection
- Challenge: Low response rates; resource-intensive; requires skilled sales team
3. Paid Digital Advertising
Reach target audiences through paid channels with precision targeting.
- Tools: Google Ads, Meta Ads, LinkedIn Ads, Newswire, Retargeting platforms
- Tactics: Search ads, display advertising, social ads, video advertising, retargeting
- Best For: Products with clear target demographics, competitive keywords
- Strength: Fast results; scalable; measurable ROI; precise targeting
- Challenge: Can be expensive; requires continuous optimization; competitive
4. Community Marketing
Build engaged communities where customers help each other and spread the word.
- Tools: Slack, Reddit, Discord, Circle, Mighty Networks, WhatsApp
- Tactics: Community forums, user groups, events, mentorship, ambassador programs
- Best For: Developer products, communities of practice, loyal user bases
- Strength: Builds loyalty; organic word-of-mouth; valuable feedback; low CAC
- Challenge: Requires active moderation; time to build critical mass
5. Partner Marketing
Leverage partner networks to co-market and reach new audiences.
- Tools: Miro, AWS Startups, Oracle Partners, Stripe, Shopify App Store
- Tactics: Partner integrations, co-marketing agreements, channel partnerships, resellers
- Best For: Complementary products, platform ecosystems, expanding market reach
- Strength: Access to established customer bases; shared costs; credibility
- Challenge: Partner alignment; revenue sharing; dependency on partners
6. Account-Based Marketing (ABM)
Treat high-value accounts as individual markets with personalized campaigns.
- Tools: Pipedrive, Hunter, Clay, 6sense, Terminus, Demandbase
- Tactics: Personalized messaging, account-targeted content, coordinated sales/marketing
- Best For: Enterprise deals, limited target accounts, high deal values
- Strength: Higher conversion rates; larger deal sizes; strong sales-marketing alignment
- Challenge: Requires detailed account research; resource intensive; not scalable to SMB
7. Product-Led Growth (PLG)
Drive adoption through the product experience itself with minimal sales friction.
- Tools: Hotjar, Amplitude, Sentry, PostHog, Intercom, Appcues
- Tactics: Free trials, freemium models, in-app onboarding, self-serve demos, product analytics
- Best For: Self-service products, SMB market, low ACV, viral potential
- Strength: Low CAC; aligns product and growth; strong PMF signals; scalable
- Challenge: Requires excellent product experience; lower price points; longer ROI
How It Works
Step 1: Understand Your Product
Define product characteristics:
- Price point and ACV (contract value)
- Sales cycle length
- Buyer type and decision-making process
- Product complexity and learning curve
- Target market size and concentration
Step 2: Evaluate Market Conditions
Assess your market dynamics:
- Competitive intensity of your keywords/channels
- Target audience location and accessibility
- Budget availability for paid channels
- Your team size and capabilities
- Timeline to revenue generation
Step 3: Score Each Motion
Rate fit for your product (1-10 scale):
- Inbound: Content creation capability, brand building timeline
- Outbound: Prospect list availability, sales team capacity
- Paid: Budget flexibility, target audience clarity, conversion potential
- Community: Existing communities, product network effects
- Partners: Complementary products, channel availability
- ABM: Deal size and account concentration
- PLG: Product trial-ability, pricing flexibility
Step 4: Design Motion Stack
Select and prioritize 2-4 motions to execute:
- Primary motion (highest potential for your business)
- Secondary motions (complementary acquisition channels)
- Motion sequencing (which to start first)
- Resource allocation across channels
Step 5: Build Execution Plan
Create 90-day implementation roadmap:
- Quick wins and early validation
- Team and tool requirements
- Success metrics for each motion
- Optimization and scaling strategy
- Budget and resource allocation
Input Format
Use $ARGUMENTS to pass:
- Product description and positioning
- Target customer profile and market
- Price point and sales cycle
- Team size and capabilities
- Budget and timeline constraints
- Existing channels or data
Output
A comprehensive GTM motions analysis including:
- Scoring of all 7 motions for your product
- Recommended motion stack (primary and secondary)
- Tool recommendations for each motion
- 90-day execution plan with milestones
- Resource and budget requirements
- Success metrics and measurement framework
- Competitive differentiation through motion choice
Framework
Based on Product Compass GTM motion analysis. Provides a systematic approach to balancing customer acquisition across multiple channels.
Tips
- Most successful products use 2-4 complementary motions
- Start with your strongest motion; add complexity gradually
- Paid channels fund growth while organic channels build long-term value
- Revisit motion mix quarterly as company scales
- Combine inbound (brand) with outbound (sales) for B2B strength
- Use PLG to reduce CAC; use paid to accelerate proven channels
Further Reading
How to use gtm-motions on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add gtm-motions
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches gtm-motions from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate gtm-motions. Access the skill through slash commands (e.g., /gtm-motions) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★44 reviews- ★★★★★Liam Martin· Dec 28, 2024
Solid pick for teams standardizing on skills: gtm-motions is focused, and the summary matches what you get after install.
- ★★★★★Soo Zhang· Dec 24, 2024
Registry listing for gtm-motions matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Lucas Jain· Dec 12, 2024
I recommend gtm-motions for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dhruvi Jain· Dec 4, 2024
Solid pick for teams standardizing on skills: gtm-motions is focused, and the summary matches what you get after install.
- ★★★★★Oshnikdeep· Nov 23, 2024
We added gtm-motions from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ira Desai· Nov 19, 2024
We added gtm-motions from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ira Dixit· Nov 15, 2024
Useful defaults in gtm-motions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Rahul Santra· Nov 3, 2024
gtm-motions is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hana Huang· Nov 3, 2024
gtm-motions reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Pratham Ware· Oct 22, 2024
Keeps context tight: gtm-motions is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 44