samwang0723/write-prd
templates/skills/write-prd/SKILL.md
Write a Product Requirements Document (PRD) using the standard TMAB template with stakeholders, user stories (Given-When-Then), success metrics, and A/B testing plans. Use when the user asks to write a PRD, create product requirements, document a feature spec, or plan a new product feature.
$ install --global
skillsauthnpx skillsauth add samwang0723/claudecode-setup write-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: Apr 17, 2026, 7:46 AM50.1s1 file scanned
SKILL.md
- name:
- write-prd
- description:
- >
write-prd
Write a Product Requirements Document (PRD) using the standard template.
Instructions
When the user asks you to write a PRD, follow these steps:
-
Gather context: Ask the user about the feature/product they want to document. Collect key information such as:
- What problem are they solving?
- Who are the stakeholders?
- What are the success metrics?
- What is the scope and timeline?
- Any existing research or competitor analysis?
-
Research the codebase and resources: If the feature relates to the current codebase, use Explore agents to understand the existing architecture, relevant files, and patterns. Search Confluence and Jira for related documentation if applicable.
-
Generate the PRD: Fill in the template below with the gathered information. Replace placeholder comments with actual content. Use clear, concise language.
-
Output: Write the PRD to a file the user specifies, or output it directly. Default filename:
docs/prd/<feature-name>-prd.md.
PRD Template
# PRD Template
## Stakeholders
| Role | Owner |
|---|---|
| **Target release** | |
| **Epic** | |
| **Document status** | |
| **Business Owner** | |
| **Document owner** | |
| **Product** | |
| **Designer** | |
| **Backends** | |
| **Frontend Devs** | |
| **Tech Spec** | |
| **QA** | |
| **Growth - CRM** | |
| **Product Analytics** | |
| **Security** | |
## PRD Edit Log
| Date | Updated by | Change |
|---|---|---|
| | | |
---
## 1. Background
> Current pain points / issue, objectives, description of feature to be built
### 1.1 What problem are we solving?
<!-- Describe the problem clearly -->
### 1.2 Existing resources
<!-- Links to related docs, designs, tech specs -->
---
## 2. Research
### 2.1 Competitor research
<!-- Competitor analysis and benchmarking -->
---
## 3. Success Metrics
| Priority | Goal | Metric | Target |
|---|---|---|---|
| P0 | | | |
| P1 | | | |
---
## 4. Approach & Scope
### 4.1 Scope
> Scope of product / feature requirements - What to build
### 4.2 Timeline
<!-- Milestones and dates -->
### 4.3 Flowchart
```mermaid
flowchart TD
A[Start] --> B[Step 1]
B --> C[Step 2]
C --> D[End]
5. Requirements
5.1 Feature category
<!-- List feature requirements here -->6. User Stories
6.1 Feature category
6.1.1 User Story
- User stories must comes with Given-When-Then style
| Field | Details | |---|---| | ID - Ticket | | | Involvement | | | User Story | | | Priority | | | Acceptance Criteria | | | Design | | | Notes | |
7. Implementation of A/B Testing and Event Tracking
The feature will only be released to specified user personas configured in Firebase, and the actions taken by users would also be tracked by using Firebase and Segment Event Tracking.
7.1 Event Tracking
| Field | Details | |---|---| | ID - Ticket | | | User Story | As an internal user, I want to implement A/B testing of the above features and have event tracking on both Firebase (for testing) and Segment (for analysis) | | Priority | Must-have | | Acceptance Criteria | The tracking plan is as below: Add link to event tracking sheet | | Notes | |
## Guidelines
- Always use **Given-When-Then** format for user stories
- Prioritize requirements as P0 (must-have), P1 (should-have), P2 (nice-to-have)
- Include mermaid flowcharts where appropriate to visualize user flows
- Link to Jira tickets (Or other tickets) and Confluence pages (Or Links) when available
- Fill in stakeholder roles based on what the user provides; leave blank if unknown
- Set the document status to "Draft" initially
Related Skills
samwang0723/write-tech-spec
development
VerifiedTrustedCommunity
Generate a technical specification document using the DDD template in template.md. Use when the user says 'write tech spec', 'create tech spec', 'technical specification', or needs a structured design document for a new feature or major change covering architecture, domain models, APIs, data design, security, and operations.
1SKILL.mdUpdated Apr 17, 2026
samwang0723/team-stop
data-ai
VerifiedTrustedCommunity
Clean up an agent team. Removes team resources, optionally cleans worktrees and branches. Use after team work is complete and merged. Use when told to "stop team", "cleanup team", "disband team".
1SKILL.mdUpdated Apr 17, 2026
samwang0723/team-status
testing
VerifiedTrustedCommunity
Check progress of an active agent team. Shows member status, completed tasks, pending work, and any messages. Use when asked "team status", "how's the team", "check team progress", "team update".
1SKILL.mdUpdated Apr 17, 2026
samwang0723/team-start
development
VerifiedTrustedCommunity
Spawn an agent team with multiple parallel Claude instances in tmux panes. Each teammate is a separate session with its own context window. Creates git worktrees and markdown state tracking alongside JSON tasks. Supports: --agents (comma-separated), --members N, --devs N. Use when told to "team up", "parallel team", "spawn a team", or "standby".
1SKILL.mdUpdated Apr 17, 2026