discovery
Skill2 starsChanged 2 months agoMITView on GitHub
A structured interview that pins down what you are actually building before you build it.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
1
Distinctive
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 19
When the frontier is empty, produce a short written summary the user could send to a stakeholder without editing: the problem, the …
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from SKILL.md by scripts/build-harnesses.mjs. Do not edit by hand; run `npm run build`. --><!-- Source: skills/deliver/discovery/SKILL.md -->Invoke the structured-interview skill.
Frame it as a discovery session: the user has an idea, a request from a customer, or a vague ask from a stakeholder, and does not yet have something that could be built, estimated or approved.
Two things to hold on to that the primitive does not assume:
The person in front of you may not be the person who decides. Ask early who has to agree to this. If a decision belongs to someone not in the room, do not let the user guess on their behalf. Record it as an open question with a named owner, and keep going. A discovery session that produces three named open questions is more useful than one that produces eight confident guesses.
Separate what is wanted from what is asked for. People arrive with a solution already chosen, usually the one they last saw demonstrated. Ask what happens today, what is wrong with it, and what would be different if this worked. Do that before discussing any Microsoft product by name. If the underlying problem does not need an agent, say so; that is a successful discovery session, not a failed one.
When the frontier is empty, produce a short written summary the user could send to a stakeholder without editing: the problem, the decisions taken and why, the open questions with owners, and what "done" means. Keep it in their vocabulary, not the product's.
Other versions23 projects use a version of this.
Word for word · 1
- RagnarPitla/microsoft-agent-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 22
- AICMO/AiCMO-Marketing-Prompt-Collection★ 229same name
- avelikiy/great_cto★ 113same name
- joelhooks/joelclaw★ 64same name
- Kanevry/session-orchestrator★ 53same name
- jantichy/claude★ 45same name
- DGouron/review-flow★ 42same name
- Dan-Cleary/fdestack★ 40same name
- tekliner/improvado-agentic-frameworks-and-skills★ 17same name
- steepy-it/steepy-apex★ 13same name
- intent-driven-dev/skills★ 9same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use brainstorm, implement and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicodianskSkillbrainstorm
Use when the user asks to add, build or change a feature and hasn't said exactly how, including a one-line request such as "add JSON output to the list command". Sizes the request first - a clear quick fix gets done directly, and anything with open choices is explored with questions before any code.
Also in 4 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 5 projects that use this
MicrosoftSkillinit
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ask-ragnar.mdcCursor rule
- .cursor/rules/assess-change-blast-radius.mdcCursor rule
- .cursor/rules/choose-agent-platform.mdcCursor rule
- .cursor/rules/copilot-studio-auth-patterns.mdcCursor rule
- .cursor/rules/copilot-studio-knowledge-grounding.mdcCursor rule
- .cursor/rules/copilot-studio-production-patterns.mdcCursor rule
- .cursor/rules/de-slop.mdcCursor rule
- .cursor/rules/discovery.mdcCursor rule
- .cursor/rules/evaluate-agent-quality.mdcCursor rule
- .cursor/rules/explain-concept.mdcCursor rule
- .cursor/rules/govern-agent-lifecycle.mdcCursor rule
- .cursor/rules/ground-agents-in-work-context.mdcCursor rule
- .cursor/rules/migrate-agent-to-skills.mdcCursor rule
- .cursor/rules/monitor-agent-telemetry.mdcCursor rule
- .cursor/rules/plan-agent-capacity-and-cost.mdcCursor rule
- .cursor/rules/power-platform-alm-connection-refs.mdcCursor rule
- .cursor/rules/respond-to-agent-incidents.mdcCursor rule
- .cursor/rules/review-copilot-studio-agent.mdcCursor rule
- .cursor/rules/structured-interview.mdcCursor rule
- .cursor/rules/what-should-i-build.mdcCursor rule
- .cursor/rules/write-a-skill.mdcCursor rule
- ask-ragnarSkill
- assess-change-blast-radiusSkill
- choose-agent-platformSkill
- copilot-studio-auth-patternsSkill
- copilot-studio-knowledge-groundingSkill
- copilot-studio-production-patternsSkill
- de-slopSkill
- evaluate-agent-qualitySkill
- explain-conceptSkill
- govern-agent-lifecycleSkill
- ground-agents-in-work-contextSkill
- migrate-agent-to-skillsSkill
- monitor-agent-telemetrySkill
- plan-agent-capacity-and-costSkill
- power-platform-alm-connection-refsSkill
- respond-to-agent-incidentsSkill
- review-copilot-studio-agentSkill
- structured-interviewSkill
- what-should-i-buildSkill
- write-a-skillSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

