product-skills

Plugin product-skills in Dragoon0x/product-skills. Commands read from the repo's manifest — 1 month ago.

Skills (70)

• cross-functional-alignment

  Bring engineering, design, research, marketing, and sales onto the same page and keep them there. Covers alignment levels, RACI clarity, and continuous maintenance. Use when teams have different understandings of what's being built, cross-team dependencies are causing problems, or alignment keeps br

• influencing-without-authority

  Get buy-in and drive alignment when you have no direct power over the people you need to move. Covers stakeholder framing, pre-wiring decisions, and building credibility over time. Use when pushing for a direction without exec authority, navigating disagreements, or when a proposal keeps getting blo

• managing-up

  Build a productive relationship with leadership by communicating effectively, managing expectations, and knowing when to push back. Use when navigating executive relationships, seeking alignment on direction, or when leadership requests conflict with team capacity.

• working-with-design

  Partner with design to create better products, not just prettier ones. Covers when to involve design, how to give useful feedback, and respecting the design process. Use when PM-design handoffs feel clunky, design feedback conversations are unproductive, or design is brought in too late.

• working-with-engineering

  Partner with engineering as a collaborator, not a ticket-writer. Covers communication norms, technical empathy, scope negotiation, and building mutual trust. Use when PM-engineering relationships feel transactional, technical decisions are made without product input, or scope conversations become ad

• working-with-gtm

  Partner with marketing, sales, and customer success to bring products to market effectively. Covers launch coordination, sales enablement, and feedback loops. Use when launches aren't driving adoption, sales can't articulate the value prop, or customer feedback isn't reaching the product team.

• changelog-voice

  Ship updates people actually want to read. Structures release notes, changelog entries, and product updates with what-changed, why-it-matters, and what-to-do-next. Use when writing changelogs or release announcements.

• conversion-copy

  Write headlines, CTAs, and value props that move people to act. Audits existing copy for weak verbs, vague claims, and missing specificity. Use when writing landing pages, hero sections, email subject lines, or any surface where words need to do real work.

• microcopy

  The small words that shape big experiences. Button labels, tooltips, confirmations, placeholders, and the 3-word strings that determine whether a product feels polished or half-finished. Use during any copy audit pass.

• product-narrative

  Tell the product story in a way that sticks. Structures origin stories, problem narratives, and transformation arcs. Use when building about pages, launch announcements, or pitch decks.

• competitive-battlecard

  Create structured competitive battlecards for sales, product, and strategy conversations. Covers positioning, objection handling, competitive landmines, and knowing when to walk away. Use when preparing for competitive deals, losing to a specific competitor, or entering a market with established pla

• feature-gap-analysis

  Identify and prioritize feature gaps between your product and competitors. Not just what's missing but which gaps matter, which don't, and which you should intentionally keep. Use when losing deals to missing features, planning roadmap with competitive context, or evaluating build-buy-partner decisi

• switching-cost-evaluation

  Analyze the real cost of switching between products — financial, technical, operational, political, and emotional. Use when trying to win customers from competitors, worried about churn to alternatives, designing migration tools, or setting pricing relative to switching friction.

• cta-patterns

  Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.

• form-optimization

  Reduce abandonment in every form, signup, and checkout flow. Multi-step logic, field reduction, inline validation, and completion micro-copy. Use when building signup flows, checkout pages, or any multi-field input.

• landing-structure

  Information architecture that guides visitors from curiosity to commitment. Enforces section order, content hierarchy, and scroll-depth logic. Use when building landing pages, product pages, or any conversion surface.

• pricing-page

  Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.

• trust-signals

  Build credibility through evidence, not claims. Patterns for social proof, testimonials, logo walls, case studies, and security badges. Use when conversion is low despite good traffic or when the product is new and unknown.

• feedback-synthesis

  Turn raw customer feedback from multiple sources into clear product insights and priorities. Covers feedback collection, pattern recognition, and separating signal from noise. Use when feedback feels overwhelming, contradictory, or when the team can't agree on what users actually want.

• problem-articulation

  Define user problems with enough clarity and specificity that the team can evaluate solutions against them. Covers problem framing, user evidence, and the gap between stated and real problems. Use when the team can't agree on what problem they're solving, solutions aren't landing, or feature request

• user-research-integration

  Turn user research into product decisions, not just reports. Covers when to research, what methods to use, and how to act on findings. Use when product direction feels disconnected from users, research exists but isn't informing decisions, or you're building on assumptions.

• communicating-decisions

  Communicate product decisions so teams understand not just what was decided but why. Covers framing, transparency about trade-offs, and handling disagreement gracefully. Use when decisions aren't sticking, teams are relitigating past calls, or when stakeholders feel left out.

• data-informed-decisions

  Use data to inform product decisions without becoming a slave to metrics. Covers when data helps, when it misleads, and how to combine quantitative and qualitative signals. Use when metrics tell confusing stories, when the team over-indexes on data, or when decisions lack any data backing.

• decision-frameworks

  Make product decisions with structure and speed, even with imperfect information. Covers decision types, reversibility, and knowing how much analysis is enough. Use when decisions are stalling, when the team is stuck in analysis paralysis, or when decisions keep getting revisited.

• launch-planning

  Plan and execute product launches that actually drive adoption, not just announcements. Covers launch tiers, cross-functional coordination, rollout strategy, and post-launch monitoring. Use when preparing a feature or product launch, coordinating across teams, or when past launches haven't moved the

• risk-management

  Identify, assess, and mitigate product risks before they become fires. Covers risk categorization, mitigation strategies, and communication frameworks. Use when planning complex launches, managing dependencies, or when too many things could go wrong.

• sprint-delivery-management

  Drive predictable delivery without micromanaging the engineering team. Covers sprint planning, blocker removal, scope negotiation, and knowing when to cut vs. push. Use when sprints consistently miss commitments, scope keeps creeping, or delivery feels chaotic.

• empty-states

  Turn dead ends into moments that build trust and guide action. Covers zero-data screens, error recovery, loading states, and retention micro-copy. Use when handling empty dashboards, failed searches, or moments where users hit a wall.

• error-recovery

  When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.

• notification-design

  Communicate without annoying. Patterns for in-app alerts, email triggers, push notification copy, and frequency capping. Use when designing notification systems or any touchpoint that competes for attention.

• onboarding-flow

  Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.

• settings-architecture

  Organize preferences and controls so people find what they need without getting lost. Information grouping, search, and defaults. Use when building settings pages, preference panels, or admin surfaces.

• launch-checklist

  Everything that needs to be true before real people see this. Pre-launch audit covering copy, meta tags, error states, mobile, performance, analytics, and the things everyone forgets. Use before any launch or public release.

• referral-mechanics

  Build sharing into the product without it feeling forced. Viral loops, invite flows, referral incentives, and the moments where asking users to share feels natural. Use when building invite systems or when organic growth needs structure.

• retention-patterns

  Design for the second visit, not just the first. Habit loops, re-engagement triggers, and value reinforcement without dark patterns. Use when retention is low, when building engagement features, or when people stop coming back.

• value-metrics

  Measure what matters, ignore what doesn't. Defines core metrics by product type, dashboards that surface real signals, and analytics events that tell the full story. Use when setting up analytics, building dashboards, or defining KPIs.

• business-acumen

  Understand how the business works so product decisions align with commercial reality. Covers revenue models, unit economics, and connecting product decisions to business outcomes. Use when product and business priorities feel disconnected, when you don't understand why leadership says no, or when bu

• metrics-measurement

  Design and maintain a metrics framework that tells you whether your product is healthy. Covers metric selection, hierarchy, and the difference between tracking and understanding. Use when metrics feel arbitrary, the team tracks too many things, or nobody agrees on what success looks like.

• outcome-thinking

  Focus product work on outcomes rather than output. Covers defining success, connecting features to results, and knowing the difference between shipping and impact. Use when the team ships lots of features but metrics don't move, when success is defined by delivery dates, or when nobody can say what

• backlog-management

  Keep the backlog useful instead of letting it become a graveyard of ideas nobody will build. Covers backlog hygiene, grooming practices, and knowing when to kill items. Use when the backlog has hundreds of stale items, sprint planning takes forever, or the team doesn't trust the backlog.

• prioritization-frameworks

  Apply structured prioritization methods to decide what to build and what to cut. Covers RICE, ICE, MoSCoW, and knowing when each framework fits. Use when the backlog is overwhelming, stakeholders disagree on priorities, or when everything feels like P0.

• time-energy-management

  Manage PM time and energy across competing demands without burning out or dropping critical work. Covers prioritization of PM activities, calendar discipline, and sustainable pace. Use when overwhelmed by meetings, losing time to reactive work, or when important strategic work keeps getting pushed.

• prd-writing

  Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.

• presentation-storytelling

  Structure presentations that persuade through narrative, not slide count. Covers story arcs, executive presentations, and knowing what to cut. Use when presenting to leadership, pitching a strategy, or when your slides aren't landing.

• stakeholder-updates

  Write status updates that executives actually read and act on. Covers structure, signal-to-noise ratio, and knowing what to escalate versus what to summarize. Use when writing weekly updates, project status reports, or board-level summaries.

• competitive-positioning

  Understand the competitive landscape and position your product clearly within it. Covers competitor analysis, differentiation strategy, and category creation vs. category entry. Use when entering a crowded market, losing deals to competitors, or when the team can't articulate why customers should ch

• north-star-setting

  Define a north star metric and product vision that aligns the team and guides daily decisions. Covers metric selection, vision articulation, and connecting daily work to long-term direction. Use when the team lacks clear direction, metrics feel arbitrary, or people can't explain what success looks l

• roadmap-planning

  Build and communicate a product roadmap that balances customer needs, business goals, and team capacity. Covers outcome-driven planning, stakeholder communication, and roadmap hygiene. Use when planning quarters, aligning stakeholders on direction, or when the roadmap feels like a feature wishlist.

• freemium-vs-paid-gate

  Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.

• packaging-strategy

  Bundle features into plans that feel natural for each customer segment. Covers feature classification, tier design, upgrade triggers, and avoiding common packaging mistakes. Use when designing tier structure, adding major features, or when upgrade rates are stagnant.

• pricing-page-teardown

  Analyze a pricing page and identify what's working, what's broken, and what's leaving money on the table. Covers tier structure, anchor pricing, CTA clarity, and anti-patterns that kill conversion. Use when designing, redesigning, or diagnosing an underperforming pricing page.

• willingness-to-pay

  Determine what customers will actually pay using structured pricing research frameworks. Covers Van Westendorp, Gabor-Granger, competitive anchoring, and practical approaches for teams without formal research budgets. Use when setting initial pricing, considering a price increase, or entering a new

• opportunity-sizing

  Estimate the potential value of a product opportunity before committing resources. Covers TAM/SAM/SOM, bottom-up and top-down estimation, scenario modeling, and key assumption identification. Use when evaluating new ideas, deciding between directions, or building a business case.

• feature-adoption-diagnosis

  Diagnose why a feature isn't getting adopted. Most features fail not because they're bad ideas but because of discoverability, onboarding, or positioning problems. Use when a shipped feature has low usage, a popular feature is declining, or deciding whether to kill, improve, or reposition something.

• funnel-drop-off-diagnosis

  Diagnose why users drop off at specific funnel steps. Moves beyond 'conversion is low' to identifying root causes and recommending specific fixes. Use when a funnel step has unexpectedly low conversion, overall funnel has degraded, or launching a new flow.

• metric-interpretation

  Understand what product metrics actually mean in context. A 3% conversion rate can be amazing or terrible depending on product type, stage, and market. Provides contextual benchmarks and interpretation frameworks. Use when evaluating whether a metric is good or bad, reporting to stakeholders, or whe

• quality-judgment

  Know when something is good enough to ship and when it needs more work. Covers quality bars, the difference between polish and perfection, and making the ship-or-hold decision. Use when debating whether to ship, setting quality standards for the team, or when quality is inconsistent across releases.

• trade-off-evaluation

  Make product trade-offs explicitly and defend them clearly. Covers scope vs. quality, speed vs. polish, and knowing what to sacrifice without destroying value. Use when facing competing priorities, deciding what to cut, or when stakeholders want everything without acknowledging constraints.

• ux-intuition

  Develop the instinct for what makes a product feel right, beyond what data can tell you. Covers quality evaluation, interaction judgment, and knowing when something is off even if you can't articulate why. Use when evaluating designs, reviewing prototypes, or when metrics say it's fine but something

• jobs-to-be-done

  Understand what people actually hire your product to do. Maps functional, emotional, and social jobs. Surfaces real competition and generates interview frameworks. Use when product direction feels unclear or when features aren't landing.

• persona-mapping

  Build user models that actually inform decisions. Maps motivations, friction points, and decision triggers beyond demographic templates. Use when building for multiple user types or when the agent needs to reason about different users.

• user-psychology

  Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.

• aha-moment-mapping

  Identify the moment when a new user first experiences your product's core value. Maps the path from signup to that moment and removes friction in between. Use when new user retention is poor, redesigning onboarding, or when the product has strong acquisition but weak activation.

• churn-signal-identification

  Identify behavioral, usage, and contextual signals that predict a customer is about to leave — before they cancel. Build an early warning system, not a postmortem. Use when churn is too high, building health scores, or designing proactive retention interventions.

• cohort-retention-analysis

  Analyze retention by cohort to understand how and why users stick around or leave. Moves beyond vanity metrics like MAU to actionable retention insights. Use when retention looks bad and you don't know where to focus, measuring impact of product changes, or comparing retention across segments.

• competitive-framing

  Position against alternatives without being negative. Maps competitive landscape, identifies differentiation axes, and generates comparison frameworks. Use when building comparison pages, handling objections, or differentiating from existing solutions.

• feature-prioritization

  Decide what to build next based on impact, not excitement. Applies scoring frameworks to feature backlogs. Use when scope is unclear, when the agent is about to build everything at once, or when deciding what ships in v1 vs v2.

• market-validation

  Test assumptions before committing resources. Generates lean validation plans, fake door tests, and interview scripts. Use before building anything expensive or when there's no evidence anyone wants what's being built.

• positioning

  Articulate why a product exists, who it serves, and what it replaces. Generates positioning statements, competitive angles, and category definitions. Use when launching something new, entering a crowded market, or when nobody can explain what the product does in one sentence.

• zero-to-one

  First principles decisions for products that don't exist yet. Helps reason about market gaps, user needs, MVP scope, and what to build first. Use when starting from scratch, scoping an MVP, or when the agent needs to think before it builds.