michaelalber/to-prd
skills/team/to-prd/SKILL.md
Converts meeting notes, feature requests, or conversation context into a structured Product Requirements Document (PRD) with goals, user stories, and binary acceptance criteria. Use when asked to "write a PRD", "turn this into a product spec", "create requirements", or "document this feature". Ported from https://github.com/mattpocock/skills (Matt Pocock).
development
Updated May 21, 2026
$ install --global
skillsauthnpx skillsauth add michaelalber/ai-toolkit to-prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 7:03 AM161.8s3 files scanned
SKILL.md
- name:
- to-prd
- audience:
- team
- source:
- mattpocock/skills
- source_commit:
- unknown
- source_note:
- Modified locally — see .matt-pocock-attribution.yml for details
- description:
- >
- Ported from https:
- //github.com/mattpocock/skills (Matt Pocock).
Convert the provided context into a structured PRD.
Instructions
- Read all provided context (conversation, notes, requirements).
- Ask any clarifying questions in one batch before writing — not one at a time.
- Write the PRD following the template in
references/prd-template.md. - Present it and ask: "Anything missing or wrong before we break this into issues?"
Key constraints
- Acceptance criteria must be binary (pass/fail), specific, and verifiable by an independent observer without asking clarifying questions.
- Non-goals are as important as goals — explicitly scope what is out of bounds.
- Open Questions must be resolved before implementation begins — flag any that block acceptance criteria from being written.
See references/acceptance-criteria-guide.md for guidance on writing good ACs.
Related Skills
michaelalber/grilling
development
VerifiedTrustedCommunity
Interviews the user relentlessly about a plan, decision, or idea — one question at a time, each with a recommended answer. Shared engine behind "grill-me" and "grill-with-docs". Use on any "grill" trigger phrase or to stress-test thinking. Do NOT use to build the plan; it ends at shared understanding, not implementation.
1SKILL.mdUpdated Jul 23, 2026
michaelalber/grill-with-docs
testing
VerifiedTrustedCommunity
Runs a relentless interview to sharpen a plan or design, capturing the decisions as ADRs and a glossary along the way. Use when the user wants to be grilled AND wants the session to leave durable domain documentation behind. Do NOT use for a throwaway stress-test with no artifacts; use grill-me instead.
1SKILL.mdUpdated Jul 23, 2026
michaelalber/vue-security-review
tools
VerifiedTrustedCommunity
OWASP-based security review of Vue/TypeScript front-ends. Detects framework (Vite/Vue CLI/Nuxt), entry points, and data flows; scans the OWASP Top 10 (2025) mapped to Vue client-side risks (raw-HTML XSS via v-html, URL/protocol injection, bundled secrets, insecure token storage, dependency CVEs, missing CSP, open redirects, router guard bypass); emits an exec summary plus graded findings. Use to audit Vue for vulnerabilities. Not for architecture grading (vue-architecture-checklist).
1SKILL.mdUpdated Jul 20, 2026
michaelalber/vue-modernization-analyzer
tools
VerifiedTrustedCommunity
Analyzes legacy Vue codebases and produces actionable modernization plans. Primary migration paths include Options API to Composition API, Vue 2 to Vue 3, Vue CLI to Vite, JavaScript to TypeScript, Vue Test Utils/Karma/Mocha to Vitest + Vue Testing Library, legacy Vuex to Pinia, and removed-in-Vue-3 pattern cleanup (filters, event bus, `$listeners`). Does NOT perform the migration — assesses, quantifies risk, and plans.
1SKILL.mdUpdated Jul 20, 2026