to-prd
Write PRD From Conversation
Read the full conversation thread first.
Understand:
- Raw requirements
- Context
- Constraints
- Open questions
- Implied user goals
Then convert the requirements into a concise PRD.
Input
- User-provided topic, request, transcript, notes, or argument text.
Output
- Problem or goal
- Users or actors
- Requirements
- Non-goals
- Constraints
- Open questions
- Acceptance criteria
More from flpbalada/fb-skills
progressive-disclosure
Reduce complexity by revealing information progressively. Use when designing
7discuss-task
Clarify ambiguous tasks before action. Use when goal, scope, success criteria, constraints, or risks are unclear.
4cognitive-fluency-psychology
Apply cognitive fluency principles to improve clarity, trust, and conversion.
4react-useeffect-avoid
Guides when NOT to use useEffect and suggests better alternatives. Use when reviewing React code, troubleshooting performance, or considering useEffect for derived state or form resets.
4discuss-code
Critically discuss code issues with compact findings. Use when code needs review for logic, simplicity, structure, naming, or maintainability.
4learn
Extract reusable patterns from the current session. Use when errors, debugging techniques, workarounds, or project conventions should become skills.
3