Best for
- Use when the problem is validated and scope is being chosen.
Source profileQuality 96/100
magnus919/agent-skills/product-methodology/SKILL.md
product-methodology
Translate validated product evidence into prioritized backlogs, decisions, specifications, and stakeholder communications. Covers RICE, MoSCoW, opportunity solution trees, decision logs, spec drafting, and audience-specific stakeholder communication. Use when the problem is validated and scope is being chosen.
- Source repository stars
- 61
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-26
- Source checked
- 2026-08-28
Decision brief
What it does: where it fits
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.
Not for
- Stakeholder discovery and interviews — load product-discovery first. This skill starts from validated evidence, not raw stakeholder conversations.
- Shaping an unbounded idea into a bet (appetite, pitch, circuit breaker) — load product-shaping before prioritization frameworks apply; this skill consumes a won bet, it does not create one.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/magnus919/agent-skills --skill "product-methodology"Safe inspection promptEditorial
Inspect the Agent Skill "product-methodology" from https://github.com/magnus919/agent-skills/blob/531ff6753784823c878c92b988c6e55266ce09a9/product-methodology/SKILL.md at commit 531ff6753784823c878c92b988c6e55266ce09a9. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Pipeline
Review the “Pipeline” section in the pinned source before continuing.
Review and apply the “Pipeline” source section. - 02
Reference Guide
Load only the reference relevant to the task:
Load only the reference relevant to the task: - 03
Templates
Review the “Templates” section in the pinned source before continuing.
Review and apply the “Templates” source section. - 04
Trigger Conditions
Prioritizing a backlog of feature proposals or initiatives
Prioritizing a backlog of feature proposals or initiativesMaking a product decision that needs a documented rationaleWriting a specification for a feature or integration - 05
When Not to Use
Stakeholder discovery and interviews — load product-discovery first. This skill starts from validated evidence, not raw stakeholder conversations.
Stakeholder discovery and interviews — load product-discovery first. This skill starts from validated evidence, not raw stakeholder conversations.Shaping an unbounded idea into a bet (appetite, pitch, circuit breaker) — load product-shaping before prioritization frameworks apply; this skill consumes a won bet, it does not create one.Interaction design, task flows, state/recovery models, or usability-study planning — use product-design-and-ux after this skill has chosen scope. This skill decides what to build and why; design-and-ux defines user-faci…
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 96/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 61 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- magnus919/agent-skills
- Skill path
- product-methodology/SKILL.md
- Commit
- 531ff6753784823c878c92b988c6e55266ce09a9
- License
- MIT
- Collected
- 2026-08-28
- Default branch
- main
View the original SKILL.md
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
VALIDATED EVIDENCE → [PRIORITIZE] → [DECIDE] → [SPECIFY] → [COMMUNICATE]
| | | |
RICE + MoSCoW Decision log Spec Stakeholder
template template briefs
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-discoveryfirst. This skill starts from validated evidence, not raw stakeholder conversations. - Shaping an unbounded idea into a bet (appetite, pitch, circuit breaker) — load product-shaping before prioritization frameworks apply; this skill consumes a won bet, it does not create one.
- Interaction design, task flows, state/recovery models, or usability-study planning — use product-design-and-ux after this skill has chosen scope. This skill decides what to build and why; design-and-ux defines user-facing behavior.
Working Method
- Confirm you have validated evidence (interview notes, usage data, competitive analysis). If not, route to
product-discovery. If the validated problem has no appetite or bounded solution yet, shape it viaproduct-shapingfirst — do not pre-shred a pitch into tasks before its bet is placed. - Prioritize with RICE when comparing unrelated proposals; use MoSCoW when scoping a time-boxed delivery.
- Log decisions as structured records with context, options, rationale, and expected outcomes.
- Write specs that define the problem, success metrics, scope boundaries, open questions, and edge cases.
- Communicate decisions in the format each audience needs — recommendation-first for executives, context-first for engineers, listening-first for customers.
Portability
This skill is intentionally host-neutral. It requires no profile system, output format, scripts, or external services. Load references directly by path — use the host agent's normal file-loading mechanism.
Provenance
| Framework | Origin | Source |
|---|---|---|
| RICE | Intercom (Sean McBride, 2016) | intercom.com/blog/rice-simple-prioritization-for-product-managers |
| MoSCoW | Dai Clegg, Oracle UK (1994); later adopted by DSDM | Agile Business Consortium: MoSCoW prioritisation |
| Opportunity Solution Trees | Teresa Torres (Product Talk) | producttalk.org/opportunity-solution-tree |
| Decision log | Synthesized from ADR practice and product management conventions | — |
| Spec template | Synthesized from common PRD practice | — |
| Stakeholder communication | Synthesized from product management communication practice | — |
This skill was ported from magnus919/hermes-profiles at commit 867a555. See references/source-index.md for the portability boundary.
Frequently asked questions
What to verify before installation and use
What does the product-methodology source document cover?
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.
How do I install product-methodology?
The source record exposes this install command: npx skills add https://github.com/magnus919/agent-skills --skill "product-methodology". Inspect the command and pinned source before running it.
Alternatives
Compare before choosing
Computed 1008
narrative-io/narrative-skills-marketplace
design-analysis
Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "
Computed 9845
objectstack-ai/objectstack
objectstack-i18n
Author ObjectStack translation bundles — object/field labels, view text, app navigation strings, automation messages — and configure locale fallback, coverage reporting, and the per-locale source layout. Use when the user is adding `*.translation.ts` files, wiring a new locale, or resolving missing-translation warnings. Do not use for general i18n library questions unrelated to ObjectStack bundles.
Computed 9825
indranilbanerjee/contentforge
cf-translate
Translate publication-ready ContentForge content into any of 15 languages at three localization levels (literal, adapted, transcreated) — preserving brand voice, keeping citation URLs and DOIs untouched, and adapting SEO keyword placements for the target market — delivered as a translated .docx plus a quality report via the brand's tracking backend. Triggers on "/contentforge:cf-translate", "translate this article to Spanish", "localize this for the German market", "make a French version of this
Computed 97603
nexscope-ai/Amazon-Skills
amazon-global-selling
Evaluate and plan Amazon marketplace expansion across countries and regions. Use when a seller asks which Amazon marketplace to enter, how to compare international demand and economics, what tax, product-compliance, logistics, localization, account, or launch workstreams to investigate, or how to build a gated global-selling roadmap. Do not use as legal, tax, customs, or certification advice.