prfaq-beagle
SolidUse 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.
Install
Quality Score: 87/100
Skill Content
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
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'.
rcode-prfaq
Working Backwards PRFAQ challenge to forge product concepts.
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.
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.
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.