Skip to content
Skills Library
Management & product · Planning

interview

/interview

Use when a person says "interview me" or asks to be interviewed about an idea or an existing design document (a board, a plan, a change) until it is understood the same way by them and the agent, or when another skill needs open decisions resolved one by one. Runs in chat and leaves the resolved decisions there, for the caller to write where they belong. Keeping the discussion as a document is brainstorm's, turning it into a plan is write-plan's.

Author
Ovich ↗
Repository
charrette ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

81/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content16 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a person says "interview me" or asks to be interviewed about an idea or an existing design document (a board, a plan, a change) until it is understood the same way by them and the agent, or when another skill needs open decisions resolved one by one. Runs in chat and leaves the resolved decisions there, for the caller to write where they belong. Keeping the discussion as a document is brainstorm's, turning it into a plan is write-plan's.

Triggers from the description

interview mes, turning it into a plan is write-plan
Original author description

Use when a person says "interview me" or asks to be interviewed about an idea or an existing design document (a board, a plan, a change) until it is understood the same way by them and the agent, or when another skill needs open decisions resolved one by one. Runs in chat and leaves the resolved decisions there, for the caller to write where they belong. Keeping the discussion as a document is brainstorm's, turning it into a plan is write-plan's.

How it works

SKILL.md has no level-two headings · 42 lines, 410 words

SKILL.md preview
---
name: interview
description: Use when a person says "interview me" or asks to be interviewed about an idea or an existing design document (a board, a plan, a change) until it is understood the same way by them and the agent, or when another skill needs open decisions resolved one by one. Runs in chat and leaves the resolved decisions there, for the caller to write where they belong. Keeping the discussion as a document is brainstorm's, turning it into a plan is write-plan's.
---

# Interview

**The interview ends at shared understanding**: the person and the agent would describe
the object the same way, and every decision is agreed or deferred. Until then, keep going.

The object is a tree of decisions. Each is answered by what can be read or by the person.

**Throw ideas in as you go.** An option the person did not list, a consequence they did not
name, a neighbouring decision the conversation points at: one line, marked as yours, beside
the question it belongs to. The interview draws the person out; it also gives them something
to push against.

**Research every decision that rests on a claim about the world**: a tool exists, it works
with our versions, the industry does it this way. Read the official source, the
specification, the package as published, its types and its changelog, and how reputable
projects solve the same problem, from their sources. State the version read and the date.
A search result or a blog is where reading starts, never where it stops.

**One option, `experiments: yes | no`.** Ask it first, with your recommendation, when the
subject makes it plausible, and later the moment reading cannot settle a claim or the
person doubts a tool. On a yes, read `references/experiments.md`. The caller stores the
answer with its decisions.

**Before each question, read**: the code, the history, the existing documents. A question about a screen goes through the `point-at` skill first.

**One decision per message, in tree order**, a branch once its parent is agreed. What
reading settles is stated with its source, and the person confirms. Where a document says
one thing and the code another, the person chooses which holds. What reading leaves open
is asked: the decision with what it depends on, the question in one sentence, the
recommended option first and marked, each option with the trade-off that decides it, and
a closing line that takes a number or a rejection of the frame. A decision left unasked
is one the implementation makes silently.

**The short mode**, offered whenever the full interview would be skipped: three questions
at most, on the decisions that change an output (kind `contract`) only, each with the
recommendation first. Every decision it leaves unasked is closed as the agent's default,
and named so.

**Close in chat**, once understanding is shared: every decision with its status and source. The caller decides where
that goes. **The caller writes decisions as rows**: read `references/decisions.md`.
Files in this package (3)
  • SKILL.md 3 KB
  • references/decisions.md 1 KB
  • references/experiments.md 1 KB

Versions

RepositoryScoreLicence
This page · Ovich/charrette81MIT
q00/ouroboros100MIT
vanducng/skills100MIT
boshu2/agentops100Apache-2.0
mthines/agent-skills100MIT
r3dlex/oh-my-auggie100Apache-2.0
YuDefine/nuxt-supabase-starter100MIT
biliboss/skills100MIT
Soe-Reh/soes-skills100MIT

Database snapshot: 13.11.2026 · package version bf0eda3acf27 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90write-plan
    Use when something non-trivial is to be built or reworked and its implementation plan has to be written, from an idea or from a board, or when a plan has to be redrawn after an increment landed. Produces, through an interview, the one plan document that holds the design, the…
  • 86brainstorm
    Use when a person wants to think an idea through and keep the discussion: a feature, a tool choice, an architecture question, before a plan or without one, with the agent through an interview. Produces a board in aiview holding the decisions, the diagrams and what was…
  • 90interview-me
    Interview the user about a plan, idea, or design through a short sequence of high-leverage questions, then summarize the direction and next step. Use when the user wants a relaxed interview, lightweight clarification, or says "interview me", without exhaustive grilling.
  • 100spec
    Interview the user about a feature or project, then write a spec they can build from. Use when the user wants to plan, scope or spec something before coding, or runs /spec with an idea.
  • 100grill-me
    Interview the user relentlessly about a plan, design, or topic, checkpointing every answer to a brainstorm file so nothing is lost. Use when the user wants to stress-test a plan, get grilled on a design, run a brainstorm or discovery session, extract what is in their head into a…
  • 100autopilot-interview
    Interview or stress-test a plan when the user requests it. Resolve routine choices and surface consequential unresolved decisions.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.