Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Uxcel-Lab/product-skills --skill idea-to-plangit clone --depth 1 https://github.com/Uxcel-Lab/product-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/uxcel-lab/product-skills/idea-to-plan)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/idea-to-plan"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/idea-to-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/idea-to-plan"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/idea-to-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00165 | $0.02971 |
| Opus 5 | $0.00082 | $0.01486 |
| Sonnet 5 | $0.00033 | $0.00594 |
| Haiku 4.5 | $0.00016 | $0.00297 |
Grade A, and why
pm-idea-to-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea → Plan (PM Creation Orchestrator) Skill
How this skill behaves (read first)
This is the front door for taking a raw idea to a build-ready plan, and the PM twin of
ux-design-from-scratch. Where pm-product-review orchestrates the validation direction
(generative → audit), this skill orchestrates the compositional direction
(generative → generative): it sequences the PM scope ladder —
problem → discovery → users → riskiest-assumption test → prioritization → spec → metrics —
pulling in each skill as the work needs it, then hands the result to pm-product-review for
validation.
It is the executable form of the compositional orchestration section (§9) of
docs/orchestration-policy.md, applied to PM. Its whole job is to avoid the failure this skill
was created to fix: a plan that is overdeveloped as a PRD and underdeveloped as a de-risked
product bet — a polished spec resting on an unexamined market and an untested
willingness-to-pay. The spec is the last rung, not the first, and it never runs before the
evidence rungs beneath it.
The one rule that makes this skill earn its place: evidence before spec. Claude's default, asked to "take me from idea to plan," rushes to a plausible-looking PRD — requirements, stories, metrics — built on an unvalidated problem and zero adoption evidence. That document looks complete, which is exactly why it's dangerous: teams build from it. This orchestrator forces the problem, the discovery evidence, and the riskiest-assumption test to come first, and keeps the spec proportionate instead of letting it swallow the plan.
When NOT to use this skill:
- One named artifact — "write me a PRD", "frame this problem", "build a prioritization matrix". Let that skill trigger directly. Explicit scope overrides orchestration.
- The strategy / launch arc — vision & strategy, competitive analysis, roadmap, GTM, launch
experiments. That is a different compositional arc (
pm-vision-strategy,pm-competitive-analysis,pm-roadmap,pm-gtm-plan,pm-experimentation-ab,pm-analytics). This skill stops at a validated, build-ready plan; offer to continue into the strategy arc rather than producing it here.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 192 lines · 165 tokens per session scan A dc1f0efa4775
pm-idea-to-plan is a skill published in the GitHub repository Uxcel-Lab/product-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 165 tokens to every session and 2,971 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
atlassian
Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via…
pm-brainstorm
A guided brainstorming workflow for exploring a new product idea before detailed research or requirements work. It collects basic information about the product, users, and problem through staged questions.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-priority
A Chinese-language procedure for ranking several product requests when time or resources are limited. It supports scoring or grouping methods such as RICE, KANO, and MoSCoW to decide what should be done first.
pm-change
A requirements-change workflow for recording a proposed change, assessing its effects, and deciding whether to approve it.