@jacfrost/autopm 0.0.1

package/resources/skills/find-skills/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** https://skills.sh/
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Check the Leaderboard First
+
+Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
+
+For example, top skills for web development include:
+- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
+- `anthropics/skills` — Frontend design, document processing (100K+ installs)
+
+### Step 3: Search for Skills
+
+If the leaderboard doesn't cover the user's need, run the find command:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+### Step 4: Verify Quality Before Recommending
+
+**Do not recommend a skill based solely on search results.** Always verify:
+
+1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.
+2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
+3. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
+
+### Step 5: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install count and source
+3. The install command they can run
+4. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+(185K installs)
+
+To install it:
+npx skills add vercel-labs/agent-skills@react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
+```
+
+### Step 6: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```

package/resources/skills/grammar-check/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: grammar-check
+description: "Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft."
+---
+# Grammar and Flow Checking
+
+You are an expert copyeditor and writing specialist. Your role is to identify grammar, logical, and flow errors in text, then provide clear, actionable fix suggestions without rewriting the entire document.
+
+## Purpose
+Analyze text for grammar, logical, and flow errors. Provide specific, focused suggestions on how to fix each issue. Focus on clarity, correctness, and readability.
+
+## Input Arguments
+- `$OBJECTIVE`: What is the intended purpose or goal of the text? (e.g., "persuade investors to fund our Series A," "explain product features to new users," "communicate company values to employees")
+- `$TEXT`: The text to review
+
+## Process
+
+### Step 1: Understand Context
+- Note the objective: Is this marketing copy, technical documentation, a presentation, an email, social media content?
+- Identify the target audience: Experts, general public, stakeholders, customers?
+- Consider tone: Formal, casual, authoritative, friendly?
+
+### Step 2: Scan for Errors
+Read through the text once, identifying:
+- **Grammar errors**: Spelling, punctuation, subject-verb agreement, tense consistency, modifier placement
+- **Logical errors**: Contradictions, unsupported claims, unclear cause-and-effect, incomplete thoughts
+- **Flow errors**: Choppy transitions, unclear organization, redundancy, passive voice overuse, vague pronouns, awkward phrasing
+
+### Step 3: Categorize Errors
+Organize findings by type:
+1. Grammar (spelling, punctuation, syntax)
+2. Logic (clarity, coherence, reasoning)
+3. Flow (transitions, sentence structure, readability, tone consistency)
+
+### Step 4: Create Fix Suggestions
+For each error, provide:
+- **Location**: Where in the text (e.g., "Paragraph 3, sentence 2")
+- **Error identified**: What's wrong
+- **Fix suggested**: How to correct it
+- **Rationale**: Why this matters (clarity, grammar rule, flow, tone)
+
+### Step 5: Prioritize
+Flag highest-impact issues first:
+- Critical: Grammar or logic errors that confuse readers
+- Important: Flow issues that hurt readability or persuasiveness
+- Minor: Stylistic suggestions or polish
+
+---
+
+## Error Categories and Examples
+
+### Grammar Errors
+
+**Spelling**
+- Example error: "buisness" instead of "business"
+- Fix: Correct spelling to "business"
+
+**Punctuation**
+- Example error: "Lets get started" (apostrophe missing in "Let's")
+- Fix: Use "Let's" (contraction of "let us")
+- Example error: Run-on sentence with multiple independent clauses not connected properly
+- Fix: Break into separate sentences or connect with a conjunction/semicolon
+
+**Subject-Verb Agreement**
+- Example error: "The team are working" (treating singular noun as plural)
+- Fix: "The team is working" (team is a collective noun, treated as singular in US English)
+
+**Tense Consistency**
+- Example error: "We launched the product last month and are seeing great results. Users report high satisfaction and prefer our solution." (mix of past and present)
+- Fix: Keep tense consistent based on timeframe
+
+**Pronoun Clarity**
+- Example error: "The manager told the designer that she should revise the mockups." (Unclear if "she" refers to manager or designer)
+- Fix: Use name or restructure: "The manager told the designer to revise the mockups."
+
+**Modifier Placement**
+- Example error: "After reviewing the proposal, the decision seemed obvious." (Who reviewed? Unclear.)
+- Fix: "After reviewing the proposal, we saw the decision was obvious."
+
+---
+
+### Logical Errors
+
+**Unsupported Claims**
+- Example error: "Our product is the best on the market because customers love it."
+- Fix: Provide evidence: "Our product has a 4.8-star rating from 2,000+ customers and achieved 40% market share in the SMB segment."
+
+**Contradictions**
+- Example error: Text says "We prioritize user privacy" but also "We share user data with 50+ third parties."
+- Fix: Clarify or reconcile the statements with detail
+
+**Incomplete Logic**
+- Example error: "The feature was launched in Q3, so adoption increased." (No proof of causation)
+- Fix: "The feature was launched in Q3; adoption increased 25% in the following month, driven by improved onboarding."
+
+**Vague Claims**
+- Example error: "Our solution saves time and money."
+- Fix: Be specific: "Our solution reduces onboarding time from 2 hours to 15 minutes and cuts operational costs by 30%."
+
+---
+
+### Flow Errors
+
+**Weak Transitions**
+- Example error: Paragraphs jump between topics without connection
+- Fix: Add transitional phrases: "In addition to this benefit," "However," "As a result," "This leads to..."
+
+**Choppy Sentences**
+- Example error: "We launched the product. We got great feedback. We iterated quickly. We improved the feature."
+- Fix: Combine related ideas: "After launching the product, we received great feedback and iterated quickly to improve the feature."
+
+**Passive Voice Overuse**
+- Example error: "The decision was made by the team to move forward with the strategy that was agreed upon." (Passive, wordy)
+- Fix: "The team decided to move forward with the agreed strategy." (Active, clearer)
+
+**Unclear Pronoun Reference**
+- Example error: "We met with the vendor about their API. It was complicated, so we decided against it." (What is "it"? The API? The vendor? The meeting?)
+- Fix: "We met with the vendor about their API, which proved too complicated, so we chose another solution."
+
+**Redundancy**
+- Example error: "Our solution is simple and easy to use; it's straightforward and uncomplicated."
+- Fix: "Our solution is simple and easy to use." (Remove redundant synonyms)
+
+**Tone Inconsistency**
+- Example error: Mix of formal ("We respectfully submit our proposal") and casual ("This is gonna blow your mind") in the same document
+- Fix: Choose consistent tone throughout
+
+---
+
+## Output Format
+
+Do NOT include the corrected text in full. Instead, provide:
+
+**[ERROR SUMMARY]**
+Count of total errors found, organized by category:
+- X grammar errors
+- X logical errors
+- X flow errors
+
+**[FIXES BY CATEGORY]**
+List all errors with fixes as bullet points. For each:
+- **Location**: Where in the text (paragraph, sentence)
+- **Error**: What's wrong (with quote from text if helpful)
+- **Fix**: How to improve it
+- **Why**: Brief rationale (clarity, grammar, engagement, etc.)
+
+**[PRIORITY FIXES]**
+Highlight the 3-5 most important changes that will have the biggest impact on readability and clarity.
+
+**[TONE AND OBJECTIVE ALIGNMENT]**
+Brief assessment of how well the text achieves its objective ($OBJECTIVE) and whether tone aligns with purpose. Suggest if tone adjustments are needed.
+
+---
+
+## Important Guidelines
+
+- **Tone**: Use straightforward, professional language. Be encouraging about the writing.
+- **Focus on clarity**: Grammar matters, but clarity is paramount. A sentence can be grammatically correct but still confusing.
+- **Use primary-school language**: Explain fixes in simple terms. Don't assume the reader knows grammar terminology.
+- **Don't rewrite**: Provide specific fix suggestions, not rewrites of entire paragraphs. Let the author maintain their voice.
+- **Include rationale**: Explain why each fix matters. This helps the author understand the principle, not just the rule.
+- **Be specific**: "Clearer" isn't helpful; say "Vague pronoun reference; 'it' could mean the API or the vendor's proposal. Change to: 'The vendor's API proved too complex.'"
+- **Consider audience**: Fixes should match the intended audience and context.
+
+---
+
+## Checklist for Review
+
+Use this checklist to ensure thorough review:
+
+- [ ] Check for spelling errors (use spell-check, manual review)
+- [ ] Check for punctuation issues (missing commas, apostrophes, periods)
+- [ ] Verify subject-verb agreement throughout
+- [ ] Check tense consistency (past, present, future should align)
+- [ ] Identify vague pronouns that could be clearer
+- [ ] Look for sentences that could be combined or split for better flow
+- [ ] Identify passive voice; flag if overused
+- [ ] Check for unsupported claims; ask "Is this proven?" or "Do we have evidence?"
+- [ ] Look for contradictions between statements
+- [ ] Check transitions between paragraphs; are they smooth?
+- [ ] Verify tone consistency with objective
+- [ ] Look for redundant words or phrases
+- [ ] Check for overly complex sentences; can they be simplified?
+- [ ] Verify that claims support the stated objective
+
+---
+
+## Examples of Effective Feedback
+
+**Poor feedback**: "This sentence is unclear."
+**Good feedback**: "The pronoun 'it' in 'the vendor's API, but it was too complex' is vague. Change to 'the vendor's API was too complex' for clarity."
+
+**Poor feedback**: "Fix the grammar here."
+**Good feedback**: "Subject-verb disagreement: 'The data show' not 'The data shows.' Collective nouns like 'data' take plural verbs in American English."
+
+**Poor feedback**: "This doesn't flow well."
+**Good feedback**: "Choppy transitions between paragraphs. Add: 'Beyond cost savings, our solution also improves employee satisfaction.' This connects the cost discussion to the next point about employee impact."
+
+---
+
+## When to Suggest No Change
+
+Not every phrase needs fixing. Leave alone:
+- Intentional style choices (short, punchy sentences for impact)
+- Correct informal language (contractions, conversational tone in casual contexts)
+- Rhetorical devices (alliteration, parallel structure for emphasis)
+- Personal voice and style (unless it undermines clarity or objective)
+
+Focus on clarity and correctness, not perfection or style uniformity.

package/resources/skills/growth-loops/SKILL.md

@@ -0,0 +1,125 @@
+---
+name: growth-loops
+description: "Identify growth loops (flywheels) for sustainable traction. Evaluates 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms, building product-led traction, or understanding how growth loops work."
+---
+# Growth Loops
+
+## Overview
+Identify and design growth loops (flywheels) that create sustainable traction. This skill evaluates five proven growth loop mechanisms to reduce reliance on paid acquisition and build product-led growth.
+
+## When to Use
+- Designing growth mechanisms for a product
+- Building sustainable viral or referral traction
+- Reducing reliance on paid acquisition
+- Analyzing competitor growth strategies
+- Optimizing product for product-led growth
+
+## The 5 Growth Loop Types
+
+### 1. Viral Loop
+Product content created by users gets shared on external platforms, bringing new users back to the product.
+- **Mechanism**: Users create content in-product → Share on social/external platforms → New users discover and signup
+- **Example**: Figma designs shared as links, Loom videos shared in emails
+- **Strength**: Exponential user acquisition if content is inherently shareable
+- **Challenge**: Requires highly shareable output and strong incentive to share
+
+### 2. Usage Loop
+Users create content or value within the product, then share it, which invites new users or drives re-engagement.
+- **Mechanism**: User creates → Shares creation → Others consume → Become engaged users
+- **Example**: Twitter threads, Medium articles, Notion templates shared publicly
+- **Strength**: Growth tied directly to product usage and network effects
+- **Challenge**: Requires content creation friction to be very low
+
+### 3. Collaboration Loop
+Users invite colleagues to co-create or collaborate within the product, expanding the user base within organizations.
+- **Mechanism**: User creates → Invites colleagues for collaboration → Colleagues discover product value
+- **Example**: Google Docs invitations, Figma team projects, Slack channels
+- **Strength**: Deep organizational penetration and high retention
+- **Challenge**: Works best for collaborative/team-based products
+
+### 4. User-Generated Loop
+Users discover new content or features through other users' creations, then create and share their own content.
+- **Mechanism**: User discovers content → Creates similar content → Shares creation → Others discover
+- **Example**: TikTok, Pinterest, YouTube trends driving creator participation
+- **Strength**: Creates content flywheel and network effects
+- **Challenge**: Requires critical mass of quality content to sustain
+
+### 5. Referral Loop
+Users invite other potential users in exchange for rewards, incentives, or social recognition.
+- **Mechanism**: User refers → Referred user joins → Referrer gets reward → Shares more referrals
+- **Example**: Dropbox referral bonus, Uber rider referrals, PayPal signup bonuses
+- **Strength**: Directly incentivizes acquisition; easy to measure ROI
+- **Challenge**: Requires valuable incentive without eroding unit economics
+
+## How It Works
+
+### Step 1: Define Product Value
+Clarify the core value users experience:
+- Primary action users take in your product
+- Value created per user action
+- Network effects present (if any)
+- Friction points in the experience
+
+### Step 2: Evaluate Loop Fit
+Assess which growth loops align with your product:
+- Product type (collaborative, content-based, utility, etc.)
+- Target user behavior and sharing habits
+- Network effects already present
+- Existing user base and engagement
+
+### Step 3: Design Loop Mechanics
+Create specific loop implementation:
+- Trigger that initiates sharing or invitations
+- Incentive for participation (intrinsic or extrinsic)
+- Ease of sharing mechanism
+- Conversion rate from invite to activation
+- Frequency of loop repetition per user
+
+### Step 4: Calculate Loop Coefficient
+Estimate growth velocity:
+- Invites/shares per user per cycle
+- Conversion rate of invites to new users
+- Net new users per cycle
+- Time per cycle iteration
+
+### Step 5: Build the Loop
+Implement the highest-leverage loop first:
+- Start with the most natural loop for your product
+- Optimize messaging and friction
+- Measure loop metrics and conversion rates
+- Compound results over time
+
+## Input Format
+Use $ARGUMENTS to pass:
+- Product description and primary user action
+- Target user demographics and behavior
+- Existing sharing/collaboration features
+- Current growth channels and metrics
+- Constraints or opportunities
+
+## Output
+A growth loops analysis including:
+- Ranked evaluation of all 5 loop types for your product
+- Recommended primary growth loop with implementation plan
+- Secondary loops to layer over time
+- Key metrics and measurement framework
+- 30-60-90 day implementation roadmap
+- Potential loop coefficient and growth projections
+
+## Framework
+Based on growth loops research by Ognjen Bošković. Focuses on compounding user acquisition through built-in, product-native sharing and collaboration mechanisms.
+
+## Tips
+- Start with one loop and master it before adding complexity
+- Viral loops compound fastest but take time to build
+- Collaboration loops create strongest retention and LTV
+- Measure loop health weekly during optimization phase
+- Combine loops for multiplicative effect once operating at scale
+
+---
+
+### Further Reading
+
+- [Product-Led Growth 101, Part 1/2](https://www.productcompass.pm/p/product-led-growth-101-12)
+- [OpenAI’s Product Leader Shares 3-Layer Distribution Framework To Win Mind & Market Share in the AI World](https://www.productcompass.pm/p/distribution-framework-ai-products)
+- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)

package/resources/skills/gtm-motions/SKILL.md

@@ -0,0 +1,155 @@
+---
+name: gtm-motions
+description: "Identify the best GTM motions and tools across 7 motion types: Inbound, Outbound, Paid Digital, Community, Partners, ABM, and PLG. Use when selecting marketing channels, choosing between inbound and outbound strategy, or planning cross-channel campaigns."
+---
+# 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
+
+- [5 GTM Principles You Should Know as a PM](https://www.productcompass.pm/p/5-gtm-principles-with-frameworks-templates)
+- [OpenAI’s Product Leader Shares 3-Layer Distribution Framework To Win Mind & Market Share in the AI World](https://www.productcompass.pm/p/distribution-framework-ai-products)
+- [Product Management vs. Product Marketing vs. Product Growth 101](https://www.productcompass.pm/p/product-management-vs-product-marketing)
+- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)