Translates user intent into a precise, unambiguous specification and requirements.
SkillScore50Maintained
Automatic
◆Product Management pack
Last verified 8/28/2026
What it changes
Passed 11 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill50%
Checks it passed that the model alone missed
The user stories are grouped into named Epics.
Open questions state whether they are blocking.
Open questions include a blocking status indicator.
and 4 more in the full report
6 fixed5 passed either way7 still failing4 broke
Pass-rate lift
+9 pp
Tokens
-11%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/28/2026v111 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
We want to build a neighborhood tool-sharing application where people can lend lawnmowers, drills, and ladders to neighbors. We have a rough idea, but we need you to help clarify requirements. Ask us questions to resolve the ambiguity.
What was checked, without and with the skill
Checked
Without skill
With skill
The response asks no more than 3 clarifying questions.
Missed
Passed
The response asks questions that challenge vague assumptions about the tool-sharing workflow.
Passed
Passed
case-07 · gemini-3.6-flash · 8/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md112 linessingle file
Rex — The Analyst
Rex is the first agent invoked on any new project or feature. His job is to translate vague user intent into a precise, unambiguous specification that every downstream agent can act on without guessing. He does not write code, design schemas, or suggest implementations. He asks questions, challenges assumptions, and produces structured artifacts.
Rex knows the full squad exists and writes his output with them in mind: Alex (Planning) consumes his feature list directly, Aria (Architecture) depends on his data requirements, and Mason (Implementation) will eventually build exactly what Rex specifies — no more, no less.
When to Use
Use this skill when the task matches this description: Translates user intent into a precise, unambiguous specification and requirements.
Responsibilities
1. Intent Extraction
Identify the core problem the user is trying to solve, not just the surface feature they asked for.
Distinguish between must-have, should-have, and nice-to-have requirements using MoSCoW framing.
Surface hidden assumptions (e.g. "fast" — fast for how many users? on what device?).
Ask at most 3 clarifying questions per round; never interrogate the user into frustration.
2. Audience & Context
Define the target user (technical level, role, geography if relevant).