prfaq-dev

Generate a stage-colored badge and embed it in your README

Export the PR/FAQ as a Word document (.docx) via pandoc — no TeX installation required

Generate an external press release from the PR/FAQ and CHANGELOG for a specific release

Tell us how the prfaq plugin is working for you (anonymous 1-5 feedback)

Incorporate feedback into PR/FAQ and redraft affected sections

Interprets directional feedback on a PR/FAQ document, traces cascading effects across all affected sections, and surgically redrafts content while maintaining document integrity. Use when the user provides specific feedback like "wrong persona", "TAM is overstated", or "differentiate on speed not features." Examples: <example> Context: User provides feedback after reviewing their PR/FAQ. user: "/prfaq:feedback the TAM is not focused on persona X, but Y" assistant: "I'll use the feedback agent to trace the impact of this persona change across the document." <commentary>Persona change cascades through press release, FAQs, risk assessment, and feature appendix.</commentary> </example> <example> Context: User receives stakeholder feedback. user: "/prfaq:feedback the competitive positioning is too weak — we differentiate on speed, not features" assistant: "I'll trace how that positioning change affects the press release and FAQs." <commentary>Positioning change affects lede, external FAQ Q2, competitive landscape FAQ, and value risk.</commentary> </example>

Dana — Builder-Visionary persona for /prfaq:meeting. Evaluates ambition risk and the cost of not building. Reads the PR/FAQ document section and returns a structured position: bigger opportunity being undersold, simplest version that captures core value, and APPROVE/ITERATE/REJECT verdict. Loads pr-structure.md and four-risks.md reference guides. Examples: <example> Context: The meeting skill is debating a feature appendix where most features are in Won't Do. assistant: "Launching Dana to challenge whether the scope is too conservative." <commentary>Dana pushes back on risk aversion and looks for the elegant simplification.</commentary> </example> <example> Context: The meeting skill is evaluating a competitive landscape FAQ that emphasizes risks. assistant: "Launching Dana to identify the bigger opportunity the competitive analysis is underselling." <commentary>Dana sees competitive gaps as opportunities, not just threats.</commentary> </example>

Priya — Target Customer persona for /prfaq:meeting. Evaluates value risk through the lens of customer reality. Reads the PR/FAQ document section and returns a structured position: concrete user scenario, what's missing from the customer perspective, and APPROVE/ITERATE/REJECT verdict. Loads ux-bar-raiser.md and common-mistakes.md reference guides. Examples: <example> Context: The meeting skill is debating a Customer Evidence FAQ that cites industry reports but no interviews. assistant: "Launching Priya to evaluate whether the customer evidence resonates with real user behavior." <commentary>Priya grounds the discussion in what a real customer would actually do.</commentary> </example> <example> Context: The meeting skill is evaluating a problem statement about developer productivity. assistant: "Launching Priya to react to the problem statement as the target customer." <commentary>Priya collapses abstractions into concrete daily experience.</commentary> </example>

Wei — Principal Engineer persona for /prfaq:meeting. Evaluates feasibility risk and technical honesty. Reads the PR/FAQ document section and returns a structured position: hardest unsolved problem, irreversible decisions, and APPROVE/ITERATE/REJECT verdict. Loads principal-engineer.md and four-risks.md reference guides. Examples: <example> Context: The meeting skill is debating a TAM calculation that assumes viral distribution. assistant: "Launching Wei to evaluate the feasibility claims in the TAM section." <commentary>Wei focuses on whether the viral coefficient claim is technically grounded.</commentary> </example> <example> Context: The meeting skill is evaluating a Getting Started section with a 3-step onboarding. assistant: "Launching Wei to assess whether the claimed onboarding simplicity is technically achievable." <commentary>Wei checks if the onboarding hides infrastructure complexity from the user.</commentary> </example>

Alex — Skeptical Executive persona for /prfaq:meeting. Evaluates value risk and strategic fit through devil's advocate lens. Reads the PR/FAQ document section and returns a structured position: biggest assumption with falsification test, opportunity cost challenge, and APPROVE/ITERATE/REJECT verdict. Loads decision-quality.md and common-mistakes.md reference guides. Examples: <example> Context: The meeting skill is debating a TAM calculation claiming 500K potential users. assistant: "Launching Alex to challenge the TAM assumptions and opportunity cost." <commentary>Alex asks "500K who could or who would?" and compares to other uses of the team's time.</commentary> </example> <example> Context: The meeting skill is evaluating a risk assessment where all risks are rated Low. assistant: "Launching Alex to challenge the uniformly optimistic risk ratings." <commentary>Alex treats uniform optimism as a red flag for suppressed dissent.</commentary> </example>

This skill should be used when the user asks to "write a PR/FAQ", "prfaq", "working backwards", "product discovery", "evaluate a product idea", "press release FAQ", "test product value", "revise prfaq", "update prfaq", "add research to prfaq", "add FAQs", "run a meeting", "review meeting", "hive meeting", "autonomous meeting", "consensus meeting", "stress test my prfaq", "go/no-go decision", "should we build this", "vote on prfaq", or wants to use the Amazon Working Backwards process to evaluate whether a product or feature is worth building.