Interview to extract intent, constraints, assumptions, and success criteria for a new system or major feature. Produces an Intake Brief (not a plan, not code).
SkillScore68Maintained
Automatic
◆Product Management pack
Last verified 8/3/2026
What it changes
Passed 15 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill68%
Checks it passed that the model alone missed
Declines to output the deployment plan.
Recommends $create-plan as the next step trigger.
Declines to output the system architecture diagram.
and 8 more in the full report
10 fixed5 passed either way3 still failing4 broke
Pass-rate lift
+27 pp
Tokens
+26%
Agent turns
0%
Response time
-2%
Model gemini-3.6-flashMeasured 8/3/2026v115 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
We want to start intake for adding dark mode support to our frontend repository. Before asking intake questions, perform a minimal scan of our project structure (such as docs, ARCHITECTURE, and ROADMAP files) to identify pre-existing constraints without modifying any files.
What was checked, without and with the skill
Checked
Without skill
With skill
Performs a read-only inspection of repository documentation files.
Missed
Passed
Refrains from modifying files during the repository context scan.
Passed
Passed
case-22 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md84 linessingle file
Intake Interview
Goal
Turn a messy, high-level goal into a crisp Intake Brief that surfaces assumptions and prevents silent drift.
This skill produces clarity, not implementation.
Non-negotiables
Operate in read-only mode. Do not modify files.
Ask questions to eliminate high-impact ambiguity.
Do not “smooth over” unknowns. Record them.
Do not output a plan or propose an architecture. Output only the Intake Brief.
Workflow
1) Minimal context scan (if in a repo)
Skim: README, docs, AGENTS/ARCHITECTURE/ROADMAP/CALIBRATION if present.
Check for REPO_PROFILE.json:
If present, treat it as authoritative for stack/tooling and do not re-ask those questions.
Identify: constraints, current architecture shape, and any non-negotiables.
2) Interview (bounded)
Ask up to 10 questions maximum. Prefer multiple-choice. Ask only what materially affects design.
Question groups:
Objective: what outcome, who uses it, what does success look like?