prfaq-beagle

Solid

Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: "work backwards", "write a PRFAQ", "press release first", "is this idea worth building", "pressure-test this concept", "filter this before brainstorm", "is this a real product". Also catches solution-first pitches ("I want to build X that does Y") and technology-first pitches ("use AI to...") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.

AI & Automation 61 stars 8 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
60
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# PRFAQ: The Concept Filter (Working Backwards) A hardcore Working Backwards coach. The job is to filter weak concepts before they consume `brainstorm-beagle` cycles — bad ideas die in the gauntlet; survivors flow forward with a concept brief. Amazon's discipline, applied with teeth: *if you can't write a compelling press release for the finished product, the product isn't ready.* <hard_gate> This skill is a filter, not a refinement tool. Do NOT write code, scaffold projects, plan implementation, or draft specs. Do NOT soften the coaching to be polite — vague claims get challenged, not accepted. The gauntlet IS the filter; skipping steps destroys the filter. Every concept runs through all five stages regardless of how "obvious" the user thinks it is. </hard_gate> ## When to use - The user has a product, internal-tool, or OSS idea and wants to know if it's worth committing to a spec. - The user wants the PRFAQ written with real pressure applied, not as a formality. - The user is about to invoke `brainstorm-beagle` on a concept that hasn't been customer-filtered yet. ## When NOT to use - The user has a concrete spec already and wants to start building → `brainstorm-beagle` or implementation planning. - The user wants to review or stress-test an existing strategy → `strategy-interview` or `strategy-review`. - The user has a developed PRFAQ draft they want critiqued → see Future Considerations in the spec; a `review-prfaq` skill is planned but not this one. ## Workflow Fi...

Details

Author
existential-birds
Repository
existential-birds/beagle
Created
5 months ago
Last Updated
today
Language
Shell
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

bmad-prfaq

Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.

2 Updated 2 days ago
mouadja02
AI & Automation Listed

rcode-prfaq

Working Backwards PRFAQ challenge to forge product concepts.

0 Updated 2 days ago
hanzlahabib
AI & Automation Listed

working-backwards

Amazon's Working Backwards product development method based on Colin Bryar and Bill Carr's "Working Backwards". Use this skill whenever the user is discussing a new product, feature, pitch, or launch narrative — even if they do not explicitly say "PR/FAQ," "press release," or "working backwards." Triggers include: (1) writing or reviewing a PR/FAQ for a new product or feature, (2) drafting the launch narrative or announcement story for something not yet built, (3) validating an idea by defining the customer experience first, (4) evaluating an internal idea pitched by a teammate or exec, (5) structuring a 6-pager or narrative memo for an exec review, (6) stress-testing a proposal with pre-mortem analysis, (7) aligning stakeholders around a product vision, (8) deciding whether an idea is worth building before writing code, (9) sharpening a fuzzy product concept into a customer-facing story, (10) running a go/no-go decision meeting on a new initiative.

0 Updated 3 days ago
tomaszstaniak
AI & Automation Listed

brainstorm-beagle

Use when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an idea for...", "help me think through this project", "what should I build", "spec this out". Also catches vague feature descriptions needing structured questioning to clarify scope. Does NOT write code, plan implementation, review strategy docs, or run strategy interviews — produces a WHAT/WHY spec through dialogue, not a HOW plan.

61 Updated today
existential-birds
AI & Automation Listed

pg-pressure-test

Pressure-test any startup idea, product bet, or new feature with the brutal honesty of a Paul Graham YC application review. Six named passes — Pressure Test the Idea (fatal flaws), Validate the Real Problem (vitamin vs painkiller), Map the Real Competition (current behavior + indirect), Find the First 10 Customers (manual traction plan), Build the MVP in 2 Weeks (riskiest assumption only), and the Brutal Verdict (strong / weak / pivot). Use when the user says "pressure test this idea", "is this a real startup", "would PG fund this", "kill or keep this idea", "is this a vitamin or a painkiller", "what's the riskiest assumption", "find me my first ten customers", "scope an MVP", "brutal feedback on this concept", or pastes a startup idea, feature concept, or one-line pitch. Triggers on `/pg-pressure-test`, `/pressure-test`, `/paul-graham`, `/brutal-verdict`, or any explicit request for PG-style critique.

0 Updated 1 weeks ago
talgacapri