Competitor Gaps
acogood/diffmode_free
Competitive gap analysis for a founder's product — a Diffmode growth-tactics think-tank research stage (prompt TT-DG-002).
Translate validated product evidence into tactical backlog decisions, prioritization, specifications, and stakeholder communications.
Install Product Methodology
$ npx skills add magnus919/agent-skills --skill product-methodology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills product-methodology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/product-methodology .claude/skills/product-methodology && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "product-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/product-methodology into .claude/skills/product-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-methodology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/agent-skills/tree/main/product-methodologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/agent-skills --skill product-methodology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills product-methodology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/product-methodology .agents/skills/product-methodology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/product-methodology into .agents/skills/product-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-methodology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill product-methodology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills product-methodology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/product-methodology .cursor/skills/product-methodology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "product-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/product-methodology into .cursor/skills/product-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-methodology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/agent-skills.git --path product-methodology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/agent-skills --skill product-methodology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills product-methodology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/product-methodology .gemini/skills/product-methodology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "product-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/product-methodology into .gemini/skills/product-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-methodology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/agent-skills product-methodologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/agent-skills --skill product-methodology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/product-methodology .github/skills/product-methodology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "product-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/product-methodology into .github/skills/product-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-methodology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill product-methodology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/agent-skills product-methodology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/product-methodology .opencode/skills/product-methodology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "product-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/product-methodology into .opencode/skills/product-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-methodology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
product-methodology- GitHub stars
- 115
- Token cost
- ~1.5k tokens
- SKILL.md length
- 586 words
- Files
- 12 (incl. references)
- Skills in repo
- 131
- Repo updated
- First seen
- Licence
- MIT
At a glance
Translate validated product evidence into tactical backlog decisions, prioritization, specifications, and stakeholder communications.
- Works in 5 steps: Confirm you have validated evidence… → Prioritize with RICE when comparing… → Log decisions as structured records with… → …
- CPO-level vision
- SKILL.md covers Pipeline, Reference Guide, Templates and Trigger Conditions, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Product Methodology is an agent skill from magnus919/agent-skills. Translate validated product evidence into tactical backlog decisions, prioritization, specifications, and stakeholder communications. Do not use this skill for CPO-level vision, positioning, or market strategy; use product-strategy for strategic direction.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including reference files (for example `README.md`, `evals/evals.json` and `references/decision-log.md`).
It sits in Product & Project Management, covering Prioritization frameworks, Internal communications and Product strategy. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- CPO-level vision
- Market strategy
- Use product-strategy for strategic direction
Example prompts
- “/product-methodology”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Confirm you have validated evidence (interview notes, usage data, competitive analysis). If not, route to product-discovery. If the…
- 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…
What it can do on your machine
Read from SKILL.md and the folder at commit 22b4723. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.comintercom.comagilebusiness.orgproducttalk.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Product Methodology loads about 1.5k tokens when it runs, and up to ~9.7k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 586 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from magnus919/agent-skills at commit 22b4723, republished under its MIT licence (© magnus919). 586 words, ~1,537 tokens.
Download SKILL.mdSave it as
.claude/skills/product-methodology/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- product-methodology
- description
- Translate validated product evidence into tactical backlog decisions, prioritization, specifications, and stakeholder communications. Do not use this skill for CPO-level vision, positioning, or market strategy; use `product-strategy` for strategic direction.
- license
- MIT
- metadata.source_repo
- https://github.com/magnus919/hermes-profiles
- metadata.source_commit
- 867a555
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 briefsReference 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.
Show full SKILL.md (252 more words)Show less
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.
Routing Boundary
Use product-strategy for CPO-level vision, positioning, market strategy, and portfolio direction. Route tactical prioritization, specifications, decision logs, and backlog sequencing back here once strategic direction and validated evidence are available; do not make portfolio strategy decisions in this skill.
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.
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files (references) in product-methodology of magnus919/agent-skills.
- SKILL.md
- README.md
- evals/evals.json
- references/decision-log.md
- references/moscow-prioritization.md
- references/opportunity-solution-trees.md
- references/rice-framework.md
- references/source-index.md
- references/spec-template.md
- references/stakeholder-communication.md
- templates/DECISION_LOG.md
- templates/SPEC.md
Open the folder on GitHubat commit 22b4723
Compare with similar skills
Product Methodology next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Product Methodology this skillmagnus919/agent-skills | 115 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Competitor Gapsacogood/diffmode_free | 163 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Opportunity Solution Treeavelikiy/great_cto | 103 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Opportunity Solution Tree Builderdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~4.5k | Automated safety check: Pass | Custom licence | |
| Product Lensaffaan-m/ECC | 277k | 2 repos | ~841 | Automated safety check: Pass | MIT | |
| Feature Investment Advisordeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~5.6k | Automated safety check: Pass | Custom licence |
Similar skills
Opportunity Solution Tree
avelikiy/great_cto
Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.
Opportunity Solution Tree Builder
deanpeters/Product-Manager-Skills
Builds an Opportunity Solution Tree from a stakeholder request: a measurable outcome, customer-problem opportunities, candidate solutions, tests and a proof-of-concept pick.
Product Lens
affaan-m/ECC
Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go/no-go recommendation, a founder review scoring…
Feature Investment Advisor
deanpeters/Product-Manager-Skills
Evaluates whether a feature deserves investment by weighing revenue connection, cost structure, ROI and strategic value, then gives a build or don't-build recommendation.
CEO Plan Review
garrytan/gstack
Reviews a plan from a founder's point of view, questioning premises and scope in one of four modes that run from expansion to reduction.
More from magnus919/agent-skills
All 131 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Related
Categories
Questions about Product Methodology
What does Product Methodology do?
Translate validated product evidence into tactical backlog decisions, prioritization, specifications, and stakeholder communications. Product Methodology is an agent skill from magnus919/agent-skills. Translate validated product evidence into tactical backlog decisions, prioritization, specifications, and stakeholder communications.
When should I use Product Methodology?
Product Methodology fits situations like: CPO-level vision; market strategy; use product-strategy for strategic direction.
How do I install Product Methodology in Claude Code?
Run `npx skills add magnus919/agent-skills --skill product-methodology -a claude-code`. Or copy the skill folder (product-methodology in magnus919/agent-skills) into .claude/skills/product-methodology in your project. Claude Code loads it when a task matches its description.
How do I install Product Methodology in Codex?
Run `npx skills add magnus919/agent-skills --skill product-methodology -a codex`. Or copy the skill folder (product-methodology in magnus919/agent-skills) into .agents/skills/product-methodology in your project. Codex loads it when a task matches its description.
Can I use Product Methodology in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill product-methodology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-methodology, .gemini/skills/product-methodology, .github/skills/product-methodology and .opencode/skills/product-methodology in your project.
What does Product Methodology need to run?
SKILL.md names no scripts, command-line tools or credentials: Product Methodology is instructions for the agent only.
Does Product Methodology access the network?
SKILL.md names 4 domains. As links in the text: github.com, intercom.com, agilebusiness.org and producttalk.org. This is read from the text; nothing was executed.
Is Product Methodology safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Product Methodology use?
Product Methodology is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Product Methodology use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.2k tokens, read only when the agent opens those files.
What are the alternatives to Product Methodology?
Skills that share tags, products or a category with Product Methodology: Competitor Gaps (acogood/diffmode_free, 163 stars), Opportunity Solution Tree (avelikiy/great_cto, 103 stars), Opportunity Solution Tree Builder (deanpeters/Product-Manager-Skills, 7.2k stars) and Product Lens (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Methodology?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 115 GitHub stars. The repository holds 131 skills in this directory. The repository was last updated on October 10, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.