intake
Skill2 starsChanged 50 days agoMITView on GitHub
Conduct a stakeholder interview to create scored backlog tickets
34 other projects use a version of this.
Adopted by
Most recently taken up by
- cdfarkas/cdfarkas-skillstheir own version, first seen Nov 8, 2026
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
- ghvinashvili/specagenttheir own version, first seen Nov 1, 2026
- bmtrnavsky/disciplined-vibe-codingtheir own version, first seen Nov 1, 2026
- AdityaZxxx/skillstheir own version, first seen Oct 20, 2026
- GopkoDev/motion-flowtheir own version, first seen Oct 20, 2026
Used with
Projects with it also use plan, triage and 7 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.
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 4 projects that use this
Microsoft AzureSkillbuild
Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.
Also in 3 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
Microsoft AzureSkillverify
End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.
Also in 4 projects that use this
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- openai/plugins★ 7.8ksame name
- Mathews-Tom/armory★ 340same name
- skillberry-ai/cap-evolve★ 69same name
- Consortium-team/project-creator★ 17same name
- bmtrnavsky/disciplined-vibe-coding★ 15same name
- awslabs/service-onboarding-accelerator-on-aws★ 7same name
- ghvinashvili/specagent★ 7same name
- ndisisnd/msg★ 6same name
- tonydzi/second-brain-starter-kit★ 6same name
- stevehansen/eidet★ 4same name
24 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.
In this repository8 other files it gives its agents.
- flow-metricsSkill
- plan-sprintSkill
- portfolioSkill
- reprioritizeSkill
- retro-accuracySkill
- sliceSkill
- standupSkill
- what-ifSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check if the project exists via project_list.
- Distinctive: line 21
Ask: "What do you need? Describe the feature or change in one sentence." Create a clear, concise ticket title from their answer.
- Distinctive: line 22
Create a clear, concise ticket title from their answer.
- Distinctive: line 27
Ask: "How valuable is this if we build it?" Anchor: 1 = nice-to-have, 5 = clearly useful, 13 = critical, 21 = existential
- Distinctive: line 31
Ask: "What happens if we don't build it?" Anchor: 1 = nothing, 5 = inconvenience, 13 = significant loss, 21 = business failure
- Distinctive: line 35
Ask: "How much effort do you think this takes?" Anchor: 1 = hours, 3 = days, 8 = weeks, 21 = months
- Distinctive: line 39
Ask: "How uncertain or complex is this?" Anchor: 1 = well-understood, 5 = some unknowns, 13 = major unknowns, 21 = research project
- Distinctive: line 43
Ask: "Any labels? (e.g. feature:checkout, team:platform)"
- Very specific: line 47
Create the ticket using ticket_create
- Distinctive: line 50
Ask: "Next story, or are we done?"
- Very specific: line 54
When done, show all created tickets in a priority-ranked table, in the order and with the weighted priorities calc_priority gives them.
“Common” is measured: kept by at least 6 in 10 of the 33 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
Stakeholder Intake Interview
Conduct a structured interview to capture stories for project $0.
Setup
- Check if the project exists via
project_list. If not, ask the user if you should create it.
Interview flow
For each story the stakeholder describes, guide them through scoring:
Step 1: Capture the story
Ask: "What do you need? Describe the feature or change in one sentence." Create a clear, concise ticket title from their answer.
Then call suggest_scores with the title (and a description, if there is one). If similar lists a ticket that looks like the same story, ask whether it's a duplicate before going on. Use references in the steps below: name an existing ticket at a score as the anchor ("Login page has benefit 8: is this more or less valuable?"), so the new ticket is scored relative to this backlog rather than in the abstract.
Step 2: Score benefit (1-21, Fibonacci)
Ask: "How valuable is this if we build it?" Anchor: 1 = nice-to-have, 5 = clearly useful, 13 = critical, 21 = existential
Step 3: Score penalty (1-21, Fibonacci)
Ask: "What happens if we don't build it?" Anchor: 1 = nothing, 5 = inconvenience, 13 = significant loss, 21 = business failure
Step 4: Score estimate (1-21, Fibonacci)
Ask: "How much effort do you think this takes?" Anchor: 1 = hours, 3 = days, 8 = weeks, 21 = months
Step 5: Score risk (1-21, Fibonacci)
Ask: "How uncertain or complex is this?" Anchor: 1 = well-understood, 5 = some unknowns, 13 = major unknowns, 21 = research project
Step 6: Tags
Ask: "Any labels? (e.g. feature:checkout, team:platform)"
After each story
- Create the ticket using
ticket_create - Tag it
state:backlogand any user-provided tags usingtag_assign - Show a summary: title, scores, and priority.
ticket_createreturns no priority: take it fromcalc_priority, which weights the scores with the project's weights, rather than working it out yourself - Ask: "Next story, or are we done?"
Wrap-up
When done, show all created tickets in a priority-ranked table, in the order and with the weighted priorities calc_priority gives them.
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.

