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 jeremylongworth-source/AgentSkills --skill product-brainstorming-planninggit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/product-brainstorming-planning)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/product-brainstorming-planning"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/product-brainstorming-planning/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/jeremylongworth-source/agentskills/product-brainstorming-planning"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/product-brainstorming-planning.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.00066 | $0.00537 |
| Opus 5.5 | $0.00026 | $0.00215 |
| Sonnet 5.5 | $0.00013 | $0.00107 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
product-brainstorming-planning 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Brainstorming Planning
Core Workflow
- Separate brainstorming from implementation planning. First clarify what should exist and why; only then decide how to build it.
- Identify user, problem, motivation, desired outcome, constraints, risks, non-goals, and decision criteria.
- Use supplied context and repository evidence first. Ask only questions whose answers materially change scope, correctness, or the chosen approach; do not require a fixed number of questions.
- Explore multiple approaches, including a small MVP, a strong version, and a risky/ambitious version.
- Surface decisions that need the user's choice. State reasonable assumptions for routine gaps and continue work that does not depend on the answer.
- Convert the selected direction into a build-ready brief with acceptance criteria.
Handoff Rule
For planning-only requests, finish with the brief and a clear next-skill recommendation. When the user also requested implementation and the direction is sufficiently specified, continue into the relevant workflow within the same task. A skill handoff is not a new approval gate. Preserve explicit planning boundaries and any required repository review. Examples:
- Game concepts: hand off to
game-skill-orchestration. - Growth, sales, or marketing ideas: hand off to
growth-strategy-orchestration. - React/Next performance ideas: hand off to
react-next-performance-optimization. - UI critique or visual polish: hand off to
visual-ui-ux-audit. - Skill improvement ideas: hand off to
skill-evaluation-iteration.
Brainstorming Modes
- Discovery: clarify the problem, audience, and success criteria.
- Divergence: generate several viable directions.
- Convergence: compare options and choose a path.
- Design shaping: define workflows, states, edge cases, and data.
- Implementation readiness: translate the idea into scope, milestones, and validation.
Output Contract
- Intent summary
- Assumptions and unknowns
- User/job/story
- Options with tradeoffs
- Recommended direction
- MVP and later versions
- Acceptance criteria
- Open questions that materially change scope
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +4 lines f5886241dad1
- 1mo ago First seen · 50 lines · 66 tokens per session scan A 9100f01a2a97
product-brainstorming-planning is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 66 tokens to every session and 537 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
analiz-task-spec
Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over.
answer-workspace-questions
Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval.
call-prep
Create or review call prep deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for call prep planning or analysis.
wicked-garden-product
Product domain skill: 13 user-invokable actions — a11y | acceptance | align | analyze | elicit | listen | mockup | screenshot | strategy | synthesize | ux | ux-review | visual-direction — backed by the rubrics in refs/ and this domain's knowledge-module sub-skills. Use when: "accessibility audit", "WCAG compliance"…
wicked-garden-swarm
Parallel verification-swarm orchestration playbook: fan out N scoped subagents over N units of work (repos / modules / files), then run a SEPARATE verifier wave that re-derives each result from a clean state — self-graded "done" is rejected. Composes the crew agents, the qe semantic-reviewer, /wicked-garden:prove…