forgelisted

# /forge Take a product idea — a sentence in the user's head — and turn it into a structured `spec/BRIEF.md` that everything downstream draws from. Forge **suggests, never interrogates.** It does not question whether the user should build the idea or what their advantage is. It clarifies *what* they want to build and surfaces structure. ## When invoked User runs `/forge` (no args) at the start of a new project, OR `/forge --refine [section]` to re-run on a section of an existing BRIEF.md. ## The 4 product questions Ask all four. Keep them tight. If an answer is vague, ask up to 2 follow-ups before moving on. Do not push back on the *value* of the idea — only on the *clarity* of intent and scope. ### Q1 — What is it, and who uses it? "In one or two sentences, what does this product do? Who is the target user, and what's the situation when they reach for it?" If the answer is abstract ("a platform for X"), ask for a concrete moment — the last time someone hit the problem this product solves and what they did instead. ### Q2 — The smallest valuable thing (v1 scope) "What is the smallest version of this that's still worth using? Strip everything optional. What remains?" Force a v1 cut. Anything beyond v1 goes to "open unknowns" or "later". ### Q3 — Non-goals "What will this product NOT do, even when tempting? Where's the scope trap?" Need at least 2 concrete non-goals. If the user can't list any, the v1 scope is under-defined — re-ask Q2. ### Q4 — Open unknowns "