Agent skill · magnus919
product-methodology
Product management frameworks for translating validated evidence into prioritized backlogs, decisions, specifications, and stakeholder communications. Covers RICE, MoSCoW, opportunity solution trees, decision logs, spec drafting, and audience-specific stakeholder communication.
What it needs
About 3k tokens when loaded.
What this skill does
Product Methodology This skill begins where discovery ends. When you have validated evidence from stakeholder conversations, competitive research, or usage data, it guides you through prioritization, decision-making, specification, and communication. Pipeline Reference Guide Load only the reference relevant to the task: Reference Load when --- --- RICE scoring You need to compare unrelated feature proposals by Reach × Impact × Confidence / Effort MoSCoW prioritization Scope is tight for a time-boxed release and you need crisp Must/Should/Could/Won't boundaries Opportunity solution trees The problem space is messy and you need to connect customer needs to build decisions without jumping to solutions Decision log You've made a decision with tradeoffs that will be questioned later — log the context and expected outcome Spec template You need a requirements document that engineers, designers, and stakeholders can all work from Stakeholder communication You're preparing a message for execs, engineers, designers, or customers — each audience needs a different format Source index Reviewing provenance, porting scope, and authoritative source links Templates Template Load when --- --- Decision log template You need a fillable decision log entry with frontmatter Spec template You need a fillable spec document with the sections provided by this methodology Trigger Conditions Load this skill when: Prioritizing a backlog of feature proposals or initiatives Making a product decision that needs a documented rationale Writing a specification for a feature or integration Communicating a product decision to different audiences (executives, engineers, designers, customers) Mapping customer opportunities to potential solutions Scoping a time-boxed release with clear boundaries A stakeholder asks "why did we decide this?" and there's no record When Not to Use Stakeholder discovery and interviews — load product-discovery first. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/product-methodology