Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs.
SkillScore68Maintained
Automatic
◆Product Management pack
Last verified 8/20/2026
What it changes
Passed 15 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill68%
Checks it passed that the model alone missed
The output uses the bug-[summary].md filename convention.
The output contains CONTEXT, TASK, CONSTRAINTS, and VERIFY headings.
The document includes CONTEXT, TASK, CONSTRAINTS, and VERIFY headings.
and 8 more in the full report
9 fixed6 passed either way7 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+50%
Agent turns
0%
Response time
-27%
Model gemini-3.6-flashMeasured 8/20/2026v215 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Users report that avatar uploads fail silently when uploading PNG files larger than 5MB on the profile settings page. Write a bug report for this issue.
What was checked, without and with the skill
Checked
Without skill
With skill
The report includes numbered step-by-step reproduction instructions.
Passed
Passed
The output uses the bug-[summary].md filename convention.
Missed
Passed
case-13 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md224 lines4 files
PM Spec Writing
Take an idea (often vague) and turn it into a specification a developer or AI agent can actually build from. Stack-agnostic. Works for new features, bug fixes, content changes, or infrastructure work.
When to use
Translating an idea into a buildable feature spec
Writing a PRD or product requirement document
Filing a bug report that someone else can act on
Scoping a project before kickoff
Prioritizing a backlog of feature requests
Writing acceptance criteria for an existing feature
Breaking a large initiative into shippable increments
When NOT to use
Quarterly or annual planning across multiple initiatives (use roadmap-planning)
Code review or debugging existing code (use code-review-web)
Design decisions for a feature already specced (use design-standards)
User research to validate an idea (use ux-research)
Required inputs
The idea, request, or problem being addressed
The audience or user affected
Any existing constraints (stack, deadlines, dependencies)
The success metric (how will you know it worked?)
If the idea is vague, the workflow's first step is clarification. Do not write specs around vagueness.
The framework: 4 phases
Every PM workflow follows the same arc. The phases are universal even if the specific outputs vary.
Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to test a page, audit a site, check for bugs, verify a deploy, run a QA sweep, or review accessibility, performance, or SEO basics. Triggers on test, QA, audit, verify, check, is it working, does it look right, broken, 404, image not loading, post-deploy check, regression test. Also triggers proactively after any significant code change or new page launch whe