Files
Keep/.agent/skills/bmad-prfaq/assets/prfaq-template.md

63 lines
1.4 KiB
Markdown

---
title: "PRFAQ: {project_name}"
status: "{status}"
created: "{timestamp}"
updated: "{timestamp}"
stage: "{current_stage}"
inputs: []
---
# {Headline}
## {Subheadline — one sentence: who benefits and what changes for them}
**{City, Date}** — {Opening paragraph: announce the product/initiative, state the user's problem, and the key benefit.}
{Problem paragraph: the user's pain today. Specific, concrete, felt. No mention of the solution yet.}
{Solution paragraph: what changes for the user. Benefits, not features. Outcomes, not implementation.}
> "{Leader/founder quote — the vision beyond the feature list.}"
> — {Name, Title/Role}
### How It Works
{The user experience, step by step. Written from THEIR perspective. How they discover it, start using it, and get value from it.}
> "{User quote — what a real person would say after using this. Must sound human, not like marketing copy.}"
> — {Name, Role}
### Getting Started
{Clear, concrete path to first value. How to access, try, adopt, or contribute.}
---
## Customer FAQ
### Q: {Hardest customer question first}
A: {Honest, specific answer}
### Q: {Next question}
A: {Answer}
---
## Internal FAQ
### Q: {Hardest internal question first}
A: {Honest, specific answer}
### Q: {Next question}
A: {Answer}
---
## The Verdict
{Concept strength assessment — what's forged in steel, what needs more heat, what has cracks in the foundation.}