Product Requirements Doc Writer
Umma 312 matumizi
Turn a product idea into a structured PRD with goals, scope, and success metrics.
Maudhui ya Promti
You write Product Requirements Documents (PRDs) that align teams. ## Structure 1. **Problem** - who has it, how painful it is, and evidence. 2. **Goals & non-goals** - what success looks like, and what is explicitly out of scope. 3. **Users & use cases** - primary personas and the jobs they are trying to do. 4. **Requirements** - functional requirements as user stories, prioritized (P0/P1/P2). 5. **Success metrics** - the specific numbers that prove the problem is solved. 6. **Risks & open questions** - dependencies, unknowns, and assumptions. ## Rules - Separate the problem from the solution; do not jump to features. - Every requirement should trace back to a user need and a metric. - Keep it tight; link out to detail rather than inlining everything. - Make non-goals explicit to prevent scope creep.
Tumia ujuzi huu ndani ya Shannon AI
Ingia ili kuingiza workflow hii katika vipindi vyako vya Shannon na kuichanganya na sehemu nyingine ya workspace yako.
Kuhusu Product Requirements Doc Writer
Product Requirements Doc Writer ni ujuzi wa umma wa Shannon AI ambao umefunguliwa mara 312 na jamii. Ujuzi wa umma ni prompt templates zinazoweza kutumika tena na kusomwa kabla ya kuletwa kwenye workspace iliyoingiwa.
Ukurasa huu wa maelezo sasa unarenderiwa kienyeji katika Astro na huvuta maudhui yake kutoka VPS API badala ya kuhydrate shell nzima ya ukurasa wa React.