interview
Use BEFORE roadmap or specify to get the idea OUT OF YOUR HEAD and onto disk — a Socratic interview that surfaces hidden assumptions, names tradeoffs, exposes imprecisions and proposes fresh angles, then writes `docs/idea-brief.md` (8 sections) so the next stage has a source to read instead of guessing. Scope is any idea (product, content, business, architecture, refactor approach); outside a git repo it stays talk-only and writes nothing. Triggers on "interview {slug}", "idea brief", "write the brief", "stress test {slug}", "challenge this", "poke holes", "rip this apart", "/sdd:interview {slug}", "бриф ідеї", "погрилити", "розбери цю ідею", "розʼєби". Runs 3 phases (understand intent → surface tradeoffs and weak spots → propose new angles) via AskUserQuestion, ends with the brief on disk + the next step. Optional — reach for it whenever the idea itself isn't settled yet; `roadmap` needs its output.
genkovich · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add genkovich/sdd --skill interviewAbout this skill
name: interview
model: inherit
effort: high
agents: []
description: >
Use BEFORE roadmap or specify to get the idea OUT OF YOUR HEAD and onto disk — a Socratic
interview that surfaces hidden assumptions, names tradeoffs, exposes imprecisions and proposes
fresh angles, then writes docs/idea-brief.md (8 sections) so the next stage has a source to
read instead of guessing. Scope is any idea (product, content, business, architecture, refactor
approach); outside a git repo it stays talk-only and writes nothing. Triggers on "interview
{slug}", "idea brief", "write the brief", "stress test {slug}", "challenge this", "poke holes",
"rip this apart", "/sdd:interview {slug}", "бриф ідеї", "погрилити", "розбери цю ідею",
"розʼєби". Runs 3 phases (understand intent → surface tradeoffs and weak spots → propose new
angles) via AskUserQuestion, ends with the brief on disk + the next step. Optional — reach for
it whenever the idea itself isn't settled yet; roadmap needs its output.
Skill: interview
Pressure-tests an idea before it becomes a roadmap or a spec, and writes down what came out.
The user shares a raw idea; across 3 phases you surface hidden assumptions, name tradeoffs,
expose imprecisions and propose fresh angles — then the survivor lands in docs/idea-brief.md.
Two things are being produced at once, and the second is the one that matters downstream:
a sharper idea in the user's head, and the context an agent cannot read anywhere else.
The repo holds what the agent can discover on its own (survey maps it); this file holds what
only the person knows. roadmap hard-refuses without a source — this is that source.
Scope: any idea. Product, content, business, architecture, refactor approach — all in scope. The boundary: this is an interview about the idea, not codebase archaeology. Ask the user to articulate the idea in words first. Consult files only if the user explicitly invites it; default is interview-first, no unprompted grep/find/read.
Language. Respond in the user's language; the instructions here are English for clarity. Brief
prose follows artifact_language, headings + frontmatter keys stay English →
../_shared/artifact-language.md.
The depth dial and the Socratic posture are SDD-wide:
→ ../_shared/interview-depth.md · ../_shared/ask-style.md
Owner
The idea's author — whoever has the thing in their head (PM / lead / engineer / the solo maintainer).
Inputs
- The raw idea, in the user's own words. Nothing else is required.
- (Optional) a
<slug>— kebab-case, short. Not given → propose 2–3 and let the user pick. - (Optional) prior notes / a ticket / links the user chooses to drop in.
The write gate — where the brief lands (and when it doesn't)
Run git rev-parse --show-toplevel once, before the final summary:
- Inside a git repo → the brief is written to
<repo root>/docs/idea-brief.md(protocol steps 6–8). This is the SDD case: the next stage reads it from disk. - Outside a repo → write nothing. The final summary is the whole artifact, the self-check
runs against the summary's own format (per
../_shared/self-check.mdstep 1), and there is no commit. A life / content / strategy idea in a scratch folder must not leave a file behind — that's the case this gate exists for.
An existing docs/idea-brief.md is updated, never silently rebuilt: read it first, and say in
the handoff which sections changed.
Protocol
- Set the depth dial. One
AskUserQuestion, then commit (default medium). The dial is SDD-wide; interview's delta — the 3–4 / 6–10 / 10–15 question budget per level and each level's posture — is the canonicalinterviewrow in../_shared/interview-depth.md(no table duplicated here). The adversarial triggers (grill / rip apart / розʼєби / погрилити) imply hard unless the user says otherwise. State the depth in one line, then start. Resolve the write gate above in the same breath (silently — onegit rev-parse, no question about it). - Phase 1 — understand the idea (see Phases).
- Phase 2 — stress-test tradeoffs and imprecisions. The core of the run.
- Phase 3 — propose new angles.
- Final summary in plain text (mini/full format below). This is what the user reads; §1–§8 of the brief are filled from it, not the other way round.
- Write — repo only. Fill
./templates/idea-brief.md→docs/idea-brief.md; setupdated_at(today) anddepth(the level this run actually used). §1 Raw idea carries the user's own words verbatim — never the polished rewrite. - Structural self-check — repo only, per
../_shared/self-check.md: re-read the file from disk and verify 5 items: (1) all eight## <n>. <Heading>sections present verbatim and none empty; (2) zero template<!-- instruction … -->comments survived into the file; (3) zero tech tokens in the body —\b(Postgres|PostgreSQL|MySQL|SQLite|Redis|Kafka|RabbitMQ|MongoDB|Elasticsearch| gRPC|GraphQL|JSONB|p95|p99)\b(the\bboundaries matter — without themchimatches inside «architecture»); (4) the frontmatter carries exactly the template's four keys (status/owner/updated_at/depth) with none invented —updated_at= today,depth= the level used,status: Draft; (5) the file exists at<repo root>/docs/idea-brief.md(test -f). Fix + re-check ≤2 cycles; surface the rest. Outside a repo the summary checked against its mini/full format IS this skill's structural self-check — nothing on disk to re-read. - Commit + handoff. Repo only: propose commit
interview: idea brief for <slug>. Then emit the stage-handoff block per [`../_shared/