One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Dragoon0xSkillDragoon0x/product-skills/skills/impact-orientation/outcome-thinking/SKILL.md
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 a feature accomplished.
Dragoon0xSkillDragoon0x/product-skills/skills/organisation-prioritization/backlog-management/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/organisation-prioritization/prioritization-frameworks/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/organisation-prioritization/time-energy-management/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pm-communication/prd-writing/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pm-communication/presentation-storytelling/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pm-communication/stakeholder-updates/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pm-strategy-vision/competitive-positioning/SKILL.md
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 choose you.
Dragoon0xSkillDragoon0x/product-skills/skills/pm-strategy-vision/north-star-setting/SKILL.md
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 like.
Dragoon0xSkillDragoon0x/product-skills/skills/pm-strategy-vision/roadmap-planning/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pricing-monetization/freemium-vs-paid-gate/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pricing-monetization/packaging-strategy/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pricing-monetization/pricing-page-teardown/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/pricing-monetization/willingness-to-pay/SKILL.md
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 segment.
Dragoon0xSkillDragoon0x/product-skills/skills/prioritization-roadmapping/opportunity-sizing/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/prioritization-roadmapping/prioritization-frameworks/SKILL.md
Score and rank product initiatives using RICE, ICE, and value-effort frameworks. Makes prioritization transparent and defensible while acknowledging that math doesn't remove all judgment. Use when the backlog is growing, stakeholders disagree on priorities, or you need to justify decisions to leadership.
Dragoon0xSkillDragoon0x/product-skills/skills/prioritization-roadmapping/roadmap-planning/SKILL.md
Build a product roadmap that balances customer needs, business goals, and technical reality. A roadmap is a strategy communicated through planned work, not a feature list with dates. Use when building quarterly or annual plans, when stakeholders pull in different directions, or when the current roadmap feels reactive.
Dragoon0xSkillDragoon0x/product-skills/skills/product-analytics/feature-adoption-diagnosis/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/product-analytics/funnel-drop-off-diagnosis/SKILL.md
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.
Dragoon0xSkillDragoon0x/product-skills/skills/product-analytics/metric-interpretation/SKILL.md
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 when a metric changes unexpectedly.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
