stakeholder-interviews
Skill1 starsChanged 37 days agoMITView on GitHub
Plan and synthesise stakeholder interviews to surface goals, constraints, assumptions and disagreements before design starts. Use when someone is starting a project, joining a new team, needs alignment, or wants to map business goals, risks and assumptions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- henrique-simoes/Istaratheir own version, first seen Sep 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- henrique-simoes/Istara★ 15same name
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.
In this repository17 other files it gives its agents.
- accessibility-researchSkill
- ai-browser-walkthroughSkill
- analytics-insightsSkill
- card-sort-tree-testSkill
- competitive-analysisSkill
- diary-studySkill
- interview-guideSkill
- jobs-to-be-doneSkill
- journey-mapSkill
- research-planSkill
- research-readoutSkill
- screener-surveySkill
- survey-designSkill
- synthetic-usersSkill
- usability-test-analysisSkill
- usability-test-planSkill
- user-personasSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 36
Don't treat a stakeholder's assumption about users as a finding.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Stakeholder interviews
Most projects fail on misalignment, not on design. Talk to the people who can kill, fund or ship the work, one by one, before anything is designed.
Who
Product, engineering, data, marketing, sales or support, legal or compliance, and whoever owns the budget. In regulated products, always compliance.
Questions to cover
- What does success look like for you, and how would we measure it?
- What has been tried before, and why didn't it work?
- What constraints are fixed (technical, legal, brand, timeline) and which are negotiable?
- What do you believe about our users that we haven't proven?
- What worries you most about this project?
- Who else should I talk to?
Synthesis
- Goals each stakeholder named, and where they conflict.
- Constraints, labelled fixed or negotiable, with who said so.
- Assumptions map: each belief about users, rated by how important it is and how much evidence exists. High importance plus low evidence is what research should test first.
- Risks and who owns them.
Output
A one page alignment summary to share back with everyone, plus the assumptions map. Disagreements are named plainly, without attributing blame.
Don't
- Don't treat a stakeholder's assumption about users as a finding.
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.