interview

Solid

Aligns on the scope of a request before any plan or implementation begins — the requirements-elicitation interview a senior engineer runs before touching code. Restates the request and diffs it against the user's words, researches the codebase so questions are specific, surfaces unknowns, non-goals, edge cases, and success criteria, then runs a batched clarifying-question interview only when research cannot resolve the ambiguity (adaptive — stays silent when the request is already crisp). Produces a confirmed brief.md artifact that downstream planning consumes, plus a readiness verdict (ready / ready-with-assumptions / blocked). Convergent and pre-plan: hands option-generation to /ideate, plan review to /critical, and scoring to /confidence. Use before autonomous work, before planning, or when a request feels underspecified. Triggers on "align on scope", "interview me", "clarify the request", "scope this", "scope alignment", "before we plan", "/interview".

Code & Development 13 stars 2 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
38
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Interview Turns an underspecified request into a confirmed, thought-through scope before a single line is planned or written. It restates and diffs the request, researches the code so its questions are specific, surfaces the unknowns and non-goals, interviews the user only where research falls short, and emits a `brief.md` that planning consumes. > **This `SKILL.md` is a thin index.** Phase procedures live in `rules/*.md` and load on demand. > A full worked run lives in [`references/interview-example.md`](./references/interview-example.md). ## Contents - [When it runs](#when-it-runs) - [Workflow](#workflow) - [Required reading by phase](#required-reading-by-phase) - [Core principles](#core-principles) - [Anti-patterns](#anti-patterns) - [Definition of done](#definition-of-done) --- ## When it runs `$ARGUMENTS` is the request to align on (free text). If `$ARGUMENTS` is empty, use the current conversation's active request; if there is none, ask what to scope — never interview against a guessed request. | Flag | Default | Meaning | | ------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | `--non-interactive` | off | Do not prompt the user. Surface the questions inside `brief.md` under `Open questions`, pr...

Details

Author
mthines
Repository
mthines/agent-skills
Created
4 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category