ederfmatos/claude-voice-bridge / .claude/skills/cy-create-prd
cy-create-prd
VerifiedCreates a Product Requirements Document through interactive brainstorming with parallel codebase and web research. Use when starting a new feature or product, building a PRD, or brainstorming requirements. Do not use for technical specifications, task breakdowns, or code implementation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| references/adr-template.md | markdown | 1.1 KB |
| references/prd-template.md | markdown | 2.8 KB |
| references/question-protocol.md | markdown | 3.3 KB |
references/prd-template.md
View on GitHub# PRD Template
Use this template to structure every Product Requirements Document. Fill each section based on brainstorming outcomes. Leave placeholder guidance in sections where information is insufficient and note them in Open Questions.
## Overview
High-level overview of the feature or product. Describe:
- What problem it solves
- Who it is for
- Why it is valuable
## Goals
Specific, measurable objectives for this feature or product:
- Success metrics and key performance indicators
- Business objectives and expected outcomes
- Target timelines or milestones
## User Stories
User stories organized by persona:
- As a [type of user], I want [action] so that [benefit]
- Primary personas and their main flows
- Secondary personas and edge cases
## Core Features
Main features grouped by priority:
- Feature name: what it does, why it is important, high-level behavior
- Functional requirements for each feature
- Interaction between features
## User Experience
User journey from first contact to regular use:
- Key personas and their goals
- Primary user flows step by step
- UI/UX considerations and accessibility requirements
- Onboarding and discoverability
## High-Level Technical Constraints
Required boundaries that shape the product without prescribing implementation:
- Required integrations with existing systems
- Compliance mandates or regulatory requirements
- Performance targets from a user perspective
- Data privacy and security requirements
Do NOT include implementation details such as specific databases, frameworks, API designs, or architecture patterns.
## Non-Goals (Out of Scope)
Explicitly excluded features and boundaries:
- Features intentionally deferred to future phases
- Adjacent problems that will not be addressed
- Boundaries of this effort
## Phased Rollout Plan
Incremental delivery plan with success criteria per phase:
### MVP (Phase 1)
- Core features included
- Success criteria to proceed to Phase 2
### Phase 2
- Additional features
- Success criteria to proceed to Phase 3
### Phase 3
- Full feature set
- Long-term success criteria
## Success Metrics
Quantifiable measures of success:
- User engagement metrics
- Performance benchmarks from a user perspective
- Business impact indicators
- Quality attributes
## Risks and Mitigations
Non-technical risks that could affect the product:
- Adoption risks and mitigation strategies
- Competitive risks
- Timeline and resource constraints
- Dependency risks on external factors
Do NOT include technical risks such as architectural complexity or technical debt.
## Architecture Decision Records
ADRs documenting key decisions made during brainstorming:
- [ADR-NNN: Title](adrs/adr-NNN.md) — One-line summary of the decision
## Open Questions
Remaining items that need clarification:
- Unclear requirements
- Edge cases requiring stakeholder input
- Dependencies on decisions not yet made
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |