skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
flaviocopes/fstack77 installs

fstack-roast

Stress-test a product idea before any code gets written. Use when you have an idea and want honest pushback, or you are not sure something is worth building.

How do I install this agent skill?

npx skills add https://github.com/flaviocopes/fstack --skill fstack-roast
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a product idea critique tool that uses a structured Q&A process to provide feedback. No malicious code, exfiltration patterns, or dangerous commands were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

/fstack-roast

Honest pushback on a product idea before anyone writes code. The goal is not to kill the idea. The goal is to find the smallest true version of it — or to save you months building a version nobody needs.

When to use

  • You have a product idea and want it challenged.
  • You are about to start building and have not answered the hard questions.
  • Someone asks "is this worth building?"

Steps

  1. Read the idea. Look at any notes, code, or links that exist.
  2. Ask up to 5 hard questions. Pick the ones this idea actually needs:
    • Who is the one person who needs this most? Describe them, specifically.
    • What do they do today to solve this, even badly? What does that cost them?
    • What is the strongest evidence someone wants this? Someone who would be upset if it vanished, not someone who said "cool".
    • What is the smallest version someone would pay for this week?
    • How will the first 100 people find it?
  3. Every question comes with answer options: 3 to 5 specific, plausible answers drawn from this idea, plus a way to type a custom one. Always include the uncomfortable option — "nobody has asked for this yet" must be as easy to pick as the flattering ones. If your environment has a tool for multiple-choice questions, use it. Otherwise letter the options (a, b, c) so the user can answer with letters or free text.
  4. Stop and wait for answers. A vague answer gets one follow-up push, not three.
  5. Deliver the roast, in three parts:
    • What is real. The parts backed by evidence or a lived problem.
    • What is wishful. The parts held up by hope. Say it plainly.
    • The wedge. The smallest version worth building. Shippable in days, not months.
  6. End with one verdict line: Build the wedge, Shrink it, or Don't build it: [reason].
  7. Stop and ask what to do next. If building, suggest /fstack-nail with the wedge as the task.

The principles it checks against

  • The status quo is the real competitor. If people solve this with "nothing", the pain is probably not real.
  • Small and shipped beats big and planned. The first version should exist in days.
  • Charge real money, simply. If the pricing needs a spreadsheet, the product is not ready.
  • Build for one specific person. Often that person is you. That is fine — say so.
  • A demo is not a product. Auth, boundaries, and failure handling arrive later, with interest.
  • Distribution is part of the product. If nobody can find it, it does not exist.
  • Boring tech ships. Pick the stack you already know.

Must NOT

  • Flatter. If the idea is weak, say so plainly and say why.
  • Kill ideas for sport. Every roast ends with the best small version, even when the verdict is harsh.
  • Invent numbers, market sizes, or fake research.
  • Ask open questions without options. The user picks or types; they never face a blank page.
  • Start planning or building. The skill ends at the verdict.

Example

User: /fstack-roast an app where AI generates personalized bedtime stories for kids

Agent: "Three questions.

  1. What evidence do you have that parents want this? a) someone has paid for something like it b) parents have asked me for it c) I saw people complaining about bedtime d) nobody has asked — it just feels right e) something else

  2. What do those parents do tonight instead? a) make up a story b) read a book they own c) YouTube d) I don't know e) something else

  3. What is the smallest version someone would pay for this week? a) one themed story pack b) a printable book c) the full app with accounts d) not sure e) something else"

User: (picks d, a, d)

Agent: "What is real: you have a four-year-old and you invent a story every night. You are the user, and the problem is lived.

What is wishful: 'parents will pay a monthly subscription'. Nobody you named has asked for this, and the status quo — making it up, or a book — costs them nothing.

The wedge: one themed story pack on a one-page site, one-time price. No app, no accounts, no generation pipeline.

Shrink it. Build the pack, show it to five parents. If three pay, /fstack-nail the next slice."

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/flaviocopes/fstack/fstack-roast">View fstack-roast on skillZs</a>