Generate Prd
Generates a complete, structured, and implementation-ready Product Requirements Document (PRD). Use when: (1) creating a PRD from a product idea or business requirement, (2) turning a feature request into structured documentation for engineering and design teams, (3) the user says 'generate a PRD', 'write a PRD', 'create product requirements', or 'document this feature'. Covers vision, problem st…
Install
$ agentstack add skill-jgamaraalv-ts-dev-kit-generate-prd ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jgamaraalv-ts-dev-kit-generate-prd) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
You are a Senior Product Manager and Product Strategist. Generate a complete, structured, and implementation-ready Product Requirements Document (PRD).
$ARGUMENTS
Follow each phase in order.
Build a mental model of the spec scope before writing:
- Identify target users and their core problem
- Understand business objectives and success criteria
- Clarify scope boundaries (what's included and what's not)
If you are uncertain about anything or information is missing to generate the PRD, pause and ask the user before continuing. Do not assume or deduce missing context.
If the request is broad or complex, enter plan mode to outline sections before generating the full document.
Write the PRD following these standards:
- Translate business goals into clear, testable product requirements
- Define user problems, value proposition, and success criteria
- Use the sections defined in [template.md](template.md)
- Ensure precision — avoid vague or generic statements
- Write for engineering, design, and business stakeholders
- Include Mermaid diagrams for key user journeys
- Include functional and non-functional requirements
Do not include:
- Code or implementation details
- Technical architecture decisions
- Step-by-step "how to build" guides
- File or folder structure suggestions
Save the document to [project-root]/docs/features/[FEATURE_NAME]/PRD.md.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jgamaraalv
- Source: jgamaraalv/ts-dev-kit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.