Discover the idea
This skill turns a messy thought into a brief: a written summary
that a different agent, the refiner, critiques. The subject does
not have to be code. The skill has no scripts/.
Role: architect. In the SDLC Brief step this agent is the
gatherer; gatherer and refiner ids, mint and resume:
Step agents. Load no
language skill on a gather-only turn:
No-language turns.
In the SDLC, the user is the operator.
Iron law
Do not write the thing. Surface the thing. The user owns every
Always-theirs and "theirs" question
(Asking the operator).
Settle a minor point yourself: write it in the brief marked your call.
your call means you settled it without asking; the user may still
change it. In an SDLC chunk, also log it as a ruling in rulings.md.
You own facts. The session ends in a brief.
Loop
0. Dump (always first)
If the thread already holds a dump, the user's unsorted text
about the idea, for example in the invoking message, use that text
as the dump and go to step 1.
Otherwise, in an SDLC chunk: end your turn and report to the
manager that you need the dump; send the user nothing. Outside the
SDLC, send this and nothing else:
Dump whatever is in your head about this. Messy is the point. Goals,
fears, constraints, half-ideas, things you already rejected, what
"done" might look like. I will not interrogate until you send it.
Wait for the dump. Send no questions in that message.
1. Reflect
- Restate the dump in one short paragraph, in the user's words,
tightened, and name what is still vague.
- In an SDLC chunk, put the restatement under Intent in the brief; the
operator corrects it at touchpoint 1. Outside the SDLC, put it at the
top of the first question round, or in the brief when no question is
left. Never send it alone.
2. Environment (only if it exists)
The environment may not be a code repo. Run this step after the dump.
- Skip this step only when there is nothing to read. Otherwise inspect
only what is actually there: working tree, notes, prior briefs, open
tickets, linked docs, public pages the user named.
- Look up every fact you can. Never ask the user what a file, ticket,
or public page already says; read it instead.
3. Options map (when alternatives exist)
- If the dump is a personal decision with no market, skip this step.
- If the idea has real options, such as tools, patterns, or prior art,
research 3–5 of them before the first question round that depends
on that choice.
- For each option, write who uses it, the ugly part, how it fits this
dump, and a source. Never claim an "industry standard" without a
source; cite one or leave the claim out.
4. Question the frontier
The idea is a design tree: each decision raises more decisions. The
frontier is every question whose prerequisites are already settled.
Resumed with a refiner's delta → each delta item is a frontier question.
Sort each frontier question as
Asking the operator says:
Always theirs first, then the three piles. Write the answered ones
into the brief. Settle the minor ones as your call. Keep the rest.
In an SDLC chunk, you are not the liaison: write each kept question
as an ask section
(Raising an ask),
list its id under Open in the brief, and send no message. Do not
wait and run no further round; write the brief next. Outside the
SDLC, ask the remaining frontier in one round. Number the questions
and give a recommended answer on each, in this format:
❓ **Q1** — **<title>**: <body, choices if any>
➡️ <recommended answer, grounded in the dump or research>
---
❓ **Q2** — **<title>**: …
➡️ …
Outside the SDLC: while you wait, do the research and look-ups
every answer needs. None left → end the turn.
Recompute the frontier. A question that depends on another question
still open this round goes in the next round.
Push back on vague words ("probably", "later", "something like").
Propose a strawman they can reject.
Cap the session at four rounds. If round 4 still widens scope, split
the idea and gather one slice. When the frontier holds no "theirs"
question, stop. Also stop when the next question cannot be answered by
talking, for example because it needs a prototype, a screenshot, or a
live system. Put those questions under Not yet specified; never invent
an answer.
5. Brief, then stop
Emit the brief in this outline:
Intent — the restatement of the dump
Decided — chose A over B because …; minor calls marked `your call`
Not yet specified — in scope, still open; Spec or a Trial settles it
Out of scope — rejected, with a lasting reason; or `no source`, `your call`
Later — wanted, deferred to a named later phase
Constraints
Assumptions — now explicit
Riskiest assumptions — most uncertain first; the top ones are the Trial slice
Standing permissions — SDLC chunk: budget, disposable environments, may create, may delete
Release permission — SDLC chunk: its own ask; recommend: ship without asking
HLD review — SDLC chunk: yes or no, with the recommendation
Guardrails we added — `Guardrail:` lines, or none
Options map — only if step 3 ran
Open — "theirs" questions still unanswered, each with its ask id
Verify later — how we would know a later build matched this
In an SDLC chunk, write the brief to brief.md in the chunk's
design folder, the folder of its asks.md
(Asks file). The
manager commits it later. End your turn: report the brief's path
and your ask ids to the manager, who runs Refine. Otherwise keep
the brief in chat; write a file only when the user asks.
Outside the SDLC, ask the user to confirm the brief. In the SDLC,
the liaison sends it at touchpoint 1 after Refine:
Chunk brief.
Stop.
Refine
The refiner runs this section, in place of the Loop, on a brief it
did not gather. It makes the brief buildable. It loads no yagni and
no language skill. It edits brief.md in place and sends the user no
message. It never changes a settled answer or the SDLC's steps and
roles. The delta is the list of items it sends back to the gatherer.
Put every requirement in one brief section. The first matching row
decides:
| The requirement |
Section |
| The user rejected it |
Out of scope, with the user's reason |
| No dump line, user answer or looked-up fact supports it |
Out of scope, no source, marked your call |
| The user asked for it, and this chunk cannot build it |
Later, with the phase that will |
| In scope and settled |
Decided |
| In scope, a detail still open |
Not yet specified |
Never delete a requirement the user asked for. Dropping one → leave
it in place and add the drop to the delta, unless it has an ask
section already.
Name each contradiction: the two lines and why both cannot hold. A
wording meets both → write it in place of both, marked your call.
None does → add it to the delta, unless it has an ask section already.
Under Riskiest assumptions, name them, most uncertain first. The top
ones are the Trial slice.
Sort every other open question as
Asking the operator says:
Always theirs first, then the three piles. Write in the answered
ones. Settle the minor ones as your call.
Each remaining question with no ask section → write one
(Raising an ask)
and list its id under Open.
Return back to Gather, with the delta, when the delta is not
empty. Otherwise return buildable: Later stays in the brief, and
every open ask goes in touchpoint 1's batch.
Ask first
- Writing
CONTEXT.md, an ADR, a ticket, or any file other than the brief, rulings.md and asks.md.
- Expanding "this idea" into "rebuild the product."
- Calling a builder before the operator confirms the brief.
Never
- Never implement, scaffold, or "just sketch the API"; emit the brief.
- Never critique the brief in the same turn; the refiner does that.
- Never recommend a tool you have not looked at this session; look first.
- Never name pantheon personas; use only Roles.
Red flags
- "I'll start the questions while you think"
- "Industry standard is X" with no source
- "Let me just write a stub so we can discuss"
- Forty questions with no recommended answers
- Loading language skills "in case we code next"
1---2name: discover-the-idea3description: use this when the user wants to think through a fuzzy idea, gather requirements, pressure-test a plan before building, or says "discover the idea", "grill me", or "interview me"; also as the SDLC refiner, which runs its Refine section. architect gatherer and refiner. do not use to implement, scaffold, or critique a finished design.4metadata:5 source: https://skillmd.com/skills/alexderz/discover-the-idea6---78# Discover the idea910This skill turns a messy thought into a **brief**: a written summary11that a different agent, the **refiner**, critiques. The subject does12not have to be code. The skill has no `scripts/`.1314Role: **architect**. In the SDLC Brief step this agent is the15**gatherer**; gatherer and refiner ids, mint and resume:16[Step agents](../sdlc/references/subagents.md#step-agents). Load no17language skill on a gather-only turn:18[No-language turns](../language-router/SKILL.md#no-language-turns).19In the SDLC, **the user** is the operator.2021## Iron law2223**Do not write the thing. Surface the thing.** The user owns every24Always-theirs and "theirs" question25([Asking the operator](../sdlc/SKILL.md#asking-the-human)).26Settle a minor point yourself: write it in the brief marked `your call`.27`your call` means you settled it without asking; the user may still28change it. In an SDLC chunk, also log it as a ruling in `rulings.md`.29You own facts. The session ends in a brief.3031## Loop3233### 0. Dump (always first)34351. If the thread already holds a **dump**, the user's unsorted text36 about the idea, for example in the invoking message, use that text37 as the dump and go to step 1.382. Otherwise, in an SDLC chunk: end your turn and report to the39 **manager** that you need the dump; send the user nothing. Outside the40 SDLC, send this and nothing else:4142 > Dump whatever is in your head about this. Messy is the point. Goals,43 > fears, constraints, half-ideas, things you already rejected, what44 > "done" might look like. I will not interrogate until you send it.45463. Wait for the dump. Send no questions in that message.4748### 1. Reflect49501. Restate the dump in one short paragraph, in the user's words,51 tightened, and name what is still vague.522. In an SDLC chunk, put the restatement under Intent in the brief; the53 operator corrects it at touchpoint 1. Outside the SDLC, put it at the54 top of the first question round, or in the brief when no question is55 left. Never send it alone.5657### 2. Environment (only if it exists)5859The environment may not be a code repo. Run this step after the dump.60611. Skip this step only when there is nothing to read. Otherwise inspect62 only what is actually there: working tree, notes, prior briefs, open63 tickets, linked docs, public pages the user named.642. Look up every fact you can. Never ask the user what a file, ticket,65 or public page already says; read it instead.6667### 3. Options map (when alternatives exist)68691. If the dump is a personal decision with no market, skip this step.702. If the idea has real options, such as tools, patterns, or prior art,71 research 3–5 of them before the first question round that depends72 on that choice.733. For each option, write who uses it, the ugly part, how it fits this74 dump, and a source. Never claim an "industry standard" without a75 source; cite one or leave the claim out.7677### 4. Question the frontier7879The idea is a **design tree**: each decision raises more decisions. The80**frontier** is every question whose prerequisites are already settled.8182Resumed with a refiner's delta → each delta item is a frontier question.83841. Sort each frontier question as85 [Asking the operator](../sdlc/SKILL.md#asking-the-human) says:86 Always theirs first, then the three piles. Write the answered ones87 into the brief. Settle the minor ones as `your call`. Keep the rest.882. In an SDLC chunk, you are not the liaison: write each kept question89 as an ask section90 ([Raising an ask](../sdlc/references/liaison.md#raising-an-ask)),91 list its id under Open in the brief, and send no message. Do not92 wait and run no further round; write the brief next. Outside the93 SDLC, ask the remaining frontier in one round. Number the questions94 and give a recommended answer on each, in this format:9596 ```97 ❓ **Q1** — **<title>**: <body, choices if any>98 ➡️ <recommended answer, grounded in the dump or research>99100 ---101102 ❓ **Q2** — **<title>**: …103 ➡️ …104 ```1051063. Outside the SDLC: while you wait, do the research and look-ups107 every answer needs. None left → end the turn.1084. Recompute the frontier. A question that depends on another question109 still open this round goes in the next round.110111Push back on vague words ("probably", "later", "something like").112Propose a strawman they can reject.113114Cap the session at four rounds. If round 4 still widens scope, split115the idea and gather one slice. When the frontier holds no "theirs"116question, stop. Also stop when the next question cannot be answered by117talking, for example because it needs a prototype, a screenshot, or a118live system. Put those questions under Not yet specified; never invent119an answer.120121### 5. Brief, then stop1221231. Emit the brief in this outline:124125 ```126 Intent — the restatement of the dump127 Decided — chose A over B because …; minor calls marked `your call`128 Not yet specified — in scope, still open; Spec or a Trial settles it129 Out of scope — rejected, with a lasting reason; or `no source`, `your call`130 Later — wanted, deferred to a named later phase131 Constraints132 Assumptions — now explicit133 Riskiest assumptions — most uncertain first; the top ones are the Trial slice134 Standing permissions — SDLC chunk: budget, disposable environments, may create, may delete135 Release permission — SDLC chunk: its own ask; recommend: ship without asking136 HLD review — SDLC chunk: yes or no, with the recommendation137 Guardrails we added — `Guardrail:` lines, or none138 Options map — only if step 3 ran139 Open — "theirs" questions still unanswered, each with its ask id140 Verify later — how we would know a later build matched this141 ```1421432. In an SDLC chunk, write the brief to `brief.md` in the chunk's144 design folder, the folder of its `asks.md`145 ([Asks file](../sdlc/references/liaison.md#asks-file)). The146 **manager** commits it later. End your turn: report the brief's path147 and your ask ids to the **manager**, who runs Refine. Otherwise keep148 the brief in chat; write a file only when the user asks.1493. Outside the SDLC, ask the user to confirm the brief. In the SDLC,150 the liaison sends it at touchpoint 1 after Refine:151 [Chunk brief](../sdlc/references/entry-brief-repo.md#chunk-brief).1524. Stop.153154## Refine155156The **refiner** runs this section, in place of the Loop, on a brief it157did not gather. It makes the brief buildable. It loads no `yagni` and158no language skill. It edits `brief.md` in place and sends the user no159message. It never changes a settled answer or the SDLC's steps and160roles. The **delta** is the list of items it sends back to the gatherer.1611621. Put every requirement in one brief section. The first matching row163 decides:164165 | The requirement | Section |166 | --- | --- |167 | The user rejected it | Out of scope, with the user's reason |168 | No dump line, user answer or looked-up fact supports it | Out of scope, `no source`, marked `your call` |169 | The user asked for it, and this chunk cannot build it | Later, with the phase that will |170 | In scope and settled | Decided |171 | In scope, a detail still open | Not yet specified |172173 Never delete a requirement the user asked for. Dropping one → leave174 it in place and add the drop to the delta, unless it has an ask175 section already.1762. Name each contradiction: the two lines and why both cannot hold. A177 wording meets both → write it in place of both, marked `your call`.178 None does → add it to the delta, unless it has an ask section already.1793. Under Riskiest assumptions, name them, most uncertain first. The top180 ones are the Trial slice.1814. Sort every other open question as182 [Asking the operator](../sdlc/SKILL.md#asking-the-human) says:183 Always theirs first, then the three piles. Write in the answered184 ones. Settle the minor ones as `your call`.1855. Each remaining question with no ask section → write one186 ([Raising an ask](../sdlc/references/liaison.md#raising-an-ask))187 and list its id under Open.1886. Return `back to Gather`, with the delta, when the delta is not189 empty. Otherwise return `buildable`: Later stays in the brief, and190 every open ask goes in touchpoint 1's batch.191192## Ask first193194- Writing `CONTEXT.md`, an ADR, a ticket, or any file other than the brief, `rulings.md` and `asks.md`.195- Expanding "this idea" into "rebuild the product."196- Calling a builder before the operator confirms the brief.197198## Never199200- Never implement, scaffold, or "just sketch the API"; emit the brief.201- Never critique the brief in the same turn; the refiner does that.202- Never recommend a tool you have not looked at this session; look first.203- Never name pantheon personas; use only [Roles](../sdlc/SKILL.md#roles).204205## Red flags206207- "I'll start the questions while you think"208- "Industry standard is X" with no source209- "Let me just write a stub so we can discuss"210- Forty questions with no recommended answers211- Loading language skills "in case we code next"