SkillsAdd

jmerta/codex-skills

manage-product-ideas

Use when the user asks to capture, clarify, document, audit, generate, compare, prioritize, validate, or realize product ideas.

First seen Aug 23, 2026

Installation

$ npx skills add jmerta/codex-skills --skill manage-product-ideas
View on skills.sh ↗ GitHub repository ↗

Summary

  • Use when the user asks to capture, clarify, document, audit, generate, compare, prioritize, validate, or realize product ideas.
  • Guides one-question-at-a-time discovery, evidence-based scoring, explicit readiness decisions, and scoped delivery without assuming a specific product, repository layout, or planning plugin.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-rbac Shared topics
microsoft/azure-skills 489K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs

Also in this package

Other skills from jmerta/codex-skills · top by installs.

npx skills add jmerta/codex-skills
ui-ux-pro-max 230 vps-checkup 134 bug-triage 43 release-notes 42 agents-md 42 regex-builder 41 plan-work 37 coding-guidelines-gen 34 dependency-upgrader 33 coding-guidelines-verify 32

Browse all from jmerta/codex-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 130
License LICENSE
Default branch main
Open issues 4
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,247 B
  • docs SUMMARY.md 346 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Manage Product Ideas

Turn a fuzzy opportunity into a documented, evidence-backed decision. Treat current code, tests, contracts, analytics, and operations as truth about the product; treat idea documents and Git history as decision context.

Read [references/idea-workflow.md](references/idea-workflow.md) before using any routed mode.

Route the request

Choose the narrowest applicable mode:

Request Mode
Raw or fuzzy idea GRILL
Create or revise an idea document DOCUMENT
Review an idea portfolio AUDIT
Propose new directions GENERATE
Choose what to do next SELECT
Build an approved idea REALIZE

For combined requests, use only applicable modes in this order: AUDIT → GENERATE → GRILL → DOCUMENT → SELECT → REALIZE.

Grill before judging

  1. Inspect available repository, product, customer, and operational evidence.
  2. Ask exactly one unresolved product decision.
  3. Include a recommended answer and its primary trade-off.
  4. Wait for the user's answer.
  5. Update the idea document immediately when documentation changes were requested.
  6. Continue until critical decisions are resolved and both sides share the same understanding.

Do not ask the user for facts that available sources can answer. Do not dump a questionnaire. Do not score, select, plan, or implement while critical branches remain unresolved.

Discover the repository's existing product-idea convention before creating files. If none exists and documentation is requested, default to docs/product-ideas/<slug>.md. Do not create a parallel hierarchy without a reason.

Preserve decision quality

  • Separate facts, assumptions, recommendations, confidence, and next actions.
  • Recover why a removed capability disappeared before proposing its return.
  • Prefer a bounded first useful outcome over platform work without a concrete customer case.
  • Below 70% confidence, choose a validation step instead of implementation.
  • Generate at most three candidates by default and persist only the candidates the user chooses.
  • Do not treat a numerical score as stronger than its evidence.

Gate realization

Before implementation, require:

  • a defined user and problem;
  • meaningful evidence or an explicit validation hypothesis;
  • a measurable outcome and stop condition;
  • a bounded first release and non-goals;
  • identified dependencies, trust boundaries, risks, rollout, and rollback;
  • resolved critical product rules.

Implementation, commits, pushes, and pull requests require their normal authorization. A selected idea or plan does not by itself authorize code changes.

Hand off

Return the current decision, confidence, strongest evidence, largest unknown, next action, and any document changed. When comparing candidates, explain why the runner-up loses instead of presenting scores without a decision.