PRFAQ — e11-prfaq

The working-backwards challenge: write the press release for the finished product before building it, then defend it through a customer FAQ and an internal FAQ. If the press release can't be written compellingly, the product isn't ready — and finding that out costs a session, not a quarter.

When to use it

• A product concept needs a go/no-go stress test before the PRD investment.
• Stakeholders need to feel what "done" is supposed to feel like, customer-first.
• The idea survived Forge idea and now deserves the full working-backwards treatment.

How to invoke

[PF] from the Analyst menu, or invoke e11-prfaq ("create a PRFAQ", "work backwards"). Accepts --headless / -H for an autonomous first draft from provided context.

What a session produces

{planning_artifacts}/prfaq-<project>.md containing:

1. Press release — the launch announcement, written as if shipped: customer, problem, solution, quote, call to action.
2. Customer FAQ — the value proposition defended from the outside in.
3. Internal FAQ — feasibility, risks, hard trade-offs, the questions your own team will ask.
4. A verdict — go, go-deeper, or no-go, with the reasoning on the page.
5. A PRD distillate — the surviving concept in a shape e11-prd (or e11-spec-flow) can consume directly.

How it behaves

• Hardcore mode. The coaching is direct; vague claims get challenged; weak ideas don't pass unexamined. When you're stuck it offers concrete suggestions and reframings.
• Research-grounded. Competitive, market, and feasibility claims are verified against current real-world data — the skill proactively researches (bundled analyzer/researcher subagents) rather than trusting yesterday's assumptions.
• Redirects when premature. Can't articulate the customer or the problem yet? It sends you to Discovery or Forge idea first rather than laundering vagueness into prose.

Gotchas

• It's a stress test, not a template. If you fill in sections without surviving the questioning, you've produced stationery, not a PRFAQ.
• Expect a workout. Budget a real session; the internal FAQ in particular goes where it hurts.
• Headless drafts still need you. --headless produces a first draft to react to — the challenge rounds are where the value is.

Customization

.foundry/custom/e11-prfaq.toml — output path, persistent_facts (e.g. your org's press-release voice), activation steps. See Customization.

Source

e11-prfaq/SKILL.md (with template, references, and two bundled subagents)

See also: Phase 1 · Forge idea · Phase 2 — PRD.