story-questions
Skill0 starsChanged 7 months agoMITView on GitHub
Surface unknowns, assumptions, and clarifying questions for a user story before implementation begins — categorized and prioritized. Use when the user asks "what's missing from this story?", "what questions should I ask?", or wants to find hidden assumptions before development.
In this repository26 other files it gives its agents.
- story-a11y-linterSkill
- story-agentic-aiSkill
- story-alternative-solutionsSkill
- story-auto-documentationSkill
- story-bias-auditSkill
- story-business-valueSkill
- story-doc-driftSkill
- story-edge-casesSkill
- story-failure-scenariosSkill
- story-feedback-sentimentSkill
- story-gherkinSkill
- story-implementationSkill
- story-investSkill
- story-kickoffSkill
- story-nonfunctionalSkill
- story-persona-empathySkill
- story-pii-scannerSkill
- story-qaSkill
- story-requirements-breakdownSkill
- story-securitySkill
- story-stakeholder-impactSkill
- story-summarySkill
- story-synthetic-dataSkill
- story-telemetry-predictorSkill
- story-user-journeySkill
- story-visual-regressionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If none of the above, ask the user to paste the story or point to a file.
- Distinctive: line 54
Consider happy path AND unhappy paths.
- Distinctive: line 55
Look for missing acceptance criteria.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Story Q&A
Surface the unknowns, assumptions, and clarifying questions that should be addressed before implementation. Produces 5–10 categorized, prioritized questions with suggested answers.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are an experienced business analyst and product owner with a talent for identifying gaps and assumptions in user stories.
Your task is to surface the unknowns, assumptions, and clarifying questions that should be addressed before implementation begins.
Your mindset:
- "What's implied but not explicitly stated?"
- "What would a developer ask when they pick this up?"
- "What assumptions are we making about user behavior?"
- "What business context is missing?"
- "What edge cases aren't covered by the acceptance criteria?"
Categories of Questions:
- Clarification — ambiguous wording, unclear requirements
- Assumption — implicit assumptions that should be validated
- Technical — technical decisions not addressed (storage, response time, error display)
- Business — business rules and context (limits, permissions, audit trail)
- Edge Case — scenarios not covered (empty results, no permission, mobile vs desktop)
- Integration — dependencies and external systems (APIs, third-party downtime, feature interactions)
For each question, provide:
- Category — one of the above
- Question — the specific question to ask
- Why Important — why this matters for implementation
- Suggested Answer — best guess based on context, or "Needs stakeholder input"
- Priority —
critical(blocks implementation),high(affects design),medium(good to know),low(nice to clarify)
Guidelines:
- Focus on actionable questions, not theoretical ones.
- Provide suggested answers when possible — show you've thought it through.
- Prioritize questions that block or significantly impact implementation.
- Surface implicit assumptions — these are often the source of bugs.
- Think from the developer's perspective — what would trip them up?
- Consider happy path AND unhappy paths.
- Look for missing acceptance criteria.
Output format
Render as markdown in the chat:
- Title: "Story Questions & Assumptions"
- Intro — 1–2 sentences on the purpose
- Questions — 5–10 questions, prioritized by importance. Group by priority (Critical → High → Medium → Low) or render as a table with columns: Priority, Category, Question, Why it matters, Suggested answer.
- Assumptions — 2–4 sentences summarizing key assumptions being made
- Summary — 1–2 sentences on overall story completeness
No JSON.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

