tai-ch0802/prd
prd/SKILL.md
Guidelines and templates for creating effective Product Requirement Documents (PRD), bridging the gap between business goals and technical implementation.
$ install --global
skillsauthnpx skillsauth add tai-ch0802/skills-bundle 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 5, 2026, 4:54 AM356.1s3 files scanned
SKILL.md
- name:
- prd
- description:
- Guidelines and templates for creating effective Product Requirement Documents (PRD), bridging the gap between business goals and technical implementation.
Product Requirement Document (PRD) Skill
This skill helps you write well-structured and logically clear Product Requirement Documents (PRD). A PRD is the core blueprint of a product — it tells us why we are building this product and what features it should have.
Why Do We Need a PRD?
- Align Goals: Ensure developers, designers, and stakeholders share a common understanding of the product.
- Reduce Ambiguity: Transform vague ideas into concrete requirements through clear text and diagrams.
- Serve as Test Baseline: The Acceptance Criteria in the PRD serve as the basis for QA testing.
PRD Core Components
A complete PRD typically contains the following sections:
- Background & Goals: Why are we doing this? What problem are we solving? What are the success metrics?
- User Stories: Who are the users? What do they want to do? What is their purpose?
- Functional Requirements: Specific descriptions of system behavior.
- Non-Functional Requirements: Performance, security, reliability constraints.
- UI/UX Flow: Page flow diagrams, wireframes, or mockup links.
- Analytics: What user behavior data needs to be tracked?
- Out of Scope: Clearly define what is not included to prevent scope creep.
How to Use This Skill
When a user presents a vague idea (e.g., "I want a feature that allows users to share bookmarks"), follow these steps:
- Initial Interview: Ask the user key questions (Who, Why, What).
- Drafting: Use
template_comprehensive.md(full version) ortemplate_simple.md(simple version) to draft the PRD. - Review: Have the user review the draft to confirm it meets expectations.
- Finalize: Once finalized, this PRD becomes the input for subsequent SA (System Analysis) and implementation phases.
Tips & Best Practices
- Use Clear Language: Avoid vague words like "might", "should"; use precise terms like "shall/must", "can".
- Use Diagrams: Use flowcharts (Mermaid) to supplement text descriptions.
- Keep It Updated: PRD is a Living Document — if requirements change, update the PRD accordingly.
Related Skills
tai-ch0802/testing-mastery
development
VerifiedTrustedCommunity
Unified testing skill — TDD workflow, unit/integration patterns, E2E/Playwright strategies. Replaces tdd-workflow + testing-patterns + webapp-testing.
2SKILL.mdUpdated May 5, 2026
tai-ch0802/skill-vetter
testing
VerifiedTrustedCommunity
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
2SKILL.mdUpdated May 5, 2026
tai-ch0802/sdd
development
VerifiedTrustedCommunity
Spec-Driven Development (SDD): A structured workflow (Requirement -> Analysis -> Implementation) enforcing explicit documentation before coding.
2SKILL.mdUpdated May 5, 2026
tai-ch0802/sa
development
VerifiedTrustedCommunity
Methodologies for System Analysis (SA), focusing on technical architecture, data flow modeling, and API design.
2SKILL.mdUpdated May 5, 2026