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/question-protocol.md
View on GitHub# Question Protocol
Structured brainstorming protocol for PRD creation. Follow these phases and rules to guide the conversation from idea to document.
## Phases
### 1. Discovery
Gather initial context about the idea or problem space.
- What is the core problem or opportunity?
- Who are the affected users?
- What prompted this initiative?
### 2. Understanding
Deepen knowledge of requirements and constraints.
- WHAT specific features do users need?
- WHY does this provide business value?
- WHO are the target users and what are their current workflows?
- What are the success criteria?
- What are the known constraints (timeline, budget, compliance)?
### 3. Direction
Decide the product approach from the gathered context.
- Weigh 2-3 distinct directions internally, considering trade-offs in scope, phasing, or strategy.
- Choose the strongest direction yourself; do NOT present a menu for the user to select.
- Record the chosen direction — with the alternatives you weighed — as an ADR.
### 4. Refinement
Refine the chosen direction with targeted follow-ups only when something is genuinely ambiguous.
- Clarify scope boundaries for the chosen direction.
- Confirm phasing and priority of features.
- Validate success criteria and metrics.
- Resolve any remaining open questions.
### 5. Creation
Generate the PRD document using the gathered context.
- Read and fill the PRD template.
- Every section should reflect confirmed decisions.
- Unresolved items go into Open Questions.
## Rules
### Interactive Question Enforcement
- Every question MUST be asked using the runtime's dedicated interactive question tool — the one that presents the question and pauses execution until the user responds.
- Do not output questions as plain text and continue generating.
- If no such tool is available, present the question as your complete message and stop generating.
### Question Limits
- Ask only one question per message. If a topic needs deeper exploration, break it into a sequence of individual questions.
- Prefer multiple-choice questions when the options can be predetermined.
- Wait for the user's answer before asking the next question.
### Progression Gates
- Must complete at least one full Understanding round before deciding the direction.
- Must have clarity on purpose, constraints, and success criteria before deciding the direction.
- Must record the chosen direction as an ADR before generating the PRD. Do not present a draft for section-by-section approval; write the file directly and let the user request changes afterward.
### Focus Boundaries
- Questions must focus on WHAT, WHY, and WHO.
- Never ask HOW, WHERE, or WHICH regarding technical implementation.
- Forbidden topics: databases, APIs, code structure, frameworks, testing strategies, architecture patterns, deployment infrastructure.
### YAGNI Principle
- Ruthlessly remove non-essential features during refinement.
- Challenge every feature: does the MVP need this?
- Defer nice-to-have features to later phases.
- Prefer smaller, well-defined scope over ambitious breadth.
### Anti-Pattern: Skipping Brainstorming For "Simple" Features
Every PRD goes through the full question protocol regardless of perceived simplicity. Simple features are where unexamined business assumptions cause the most rework. The brainstorming can be brief, but it must happen.
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 |