intake
Skill1 starsChanged 4 months agoMITView on GitHub
Delegation intake interview. Use before delegating any significant or ambiguous task to a specialist. Runs a 6-question interview that forces precision, then compresses the answers into the spawn prompt the specialist receives. Skip for small, unambiguous tasks (filing, list updates, lookups).
34 other projects use a version of this.
Adopted by
Most recently taken up by
- sebs/rewelotheir own version, first seen Nov 15, 2026
- skillberry-ai/cap-evolvetheir own version, first seen Nov 8, 2026
- 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
Used with
Projects with it also use triage, plan 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.
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 5 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
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
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 4 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★ 70same name
- bmtrnavsky/disciplined-vibe-coding★ 19same name
- Consortium-team/project-creator★ 17same 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 repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- fd-blocker-sweepSkill
- fd-firm-onboardSkill
- fd-onsite-availabilitySkill
- fd-portfolio-rollupSkill
- fd-reconcileSkill
- full-sweepSkill
- process-meetingsSkill
- safe-mvSkill
- slack-recapSkill
- steSkill
- sweep-binderSkill
- sweep-jiraSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Run it when the task is significant or the brief is ambiguous: a deck, a research piece, a multi-step deliverable, anything where a wrong …
- Distinctive: line 16
Do not: run it for small, unambiguous tasks (filing a note, updating a list, a lookup, archiving an inbox file).
- Distinctive: line 18
When in doubt, ask Jeff: "This one's worth a quick intake.
- Distinctive: line 22
Ask one question at a time.
- Distinctive: line 23
After each answer, reflect back what you heard in one sentence, then continue.
- Distinctive: line 47
Persist durable shared language to memory: Check whether any term from Q3 or decision from Q4 is worth keeping across sessions.
- Distinctive: line 50
Before writing a memory, apply the filter:
- Very specific: line 55
Only persist entries that pass all three.
“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
Intake — Delegation Brief
A specialist you spawn sees only the prompt you hand them. No session history, no memory of past conversations, no context except what you write. This interview turns that delegation brief from a guess into a decision.
When to run this
- Run it when the task is significant or the brief is ambiguous: a deck, a research piece, a multi-step deliverable, anything where a wrong interpretation costs real rework.
- Do not run it for small, unambiguous tasks (filing a note, updating a list, a lookup, archiving an inbox file). The friction would just train Jeff to skip it.
- When in doubt, ask Jeff: "This one's worth a quick intake. Two minutes?" then proceed.
The interview
Ask one question at a time. Wait for the answer before moving on. After each answer, reflect back what you heard in one sentence, then continue. The harder a question is to answer, the more useful it is — that difficulty is the language gap a specialist would otherwise fill with a guess.
- The task — What are you trying to make, decide, or get done? One sentence. If it takes more than one sentence, the scope isn't clear yet.
- Done looks like — What's the deliverable that lands in
owners_inbox/, in what format, and what is the checkable exit condition: the specific test, rubric, count, or sign-off that tells the specialist to stop iterating? A vague aspiration ("it should feel right") is not an exit condition — push for something that can pass or fail. (Coaching: if Jeff's answer is fuzzy, ask: "How would you decide in under 60 seconds whether the specialist's draft is accepted or needs another pass?" Press until the answer is testable.) - Shared language — What terms, named things, people, or prior decisions does this touch that the specialist wouldn't know cold? For each: what does it mean in your context?
- Locked decisions — What's already decided and not up for re-litigation? For each: the decision, and why it's locked.
- The failure mode — What does a bad deliverable look like? What's the real cost of getting it wrong? This becomes the guardrail in the spawn prompt.
- The one thing — If this has to get one thing right above all else, what is it? This becomes the headline instruction to the specialist.
After the interview
- Route. Name the specialist who should own this (or flag that a new hire is needed via Scout + Forge). Stay the single point of contact.
- Compress into the spawn prompt. Fold the six answers into the delegation prompt:
- Q1 → the objective line
- Q2 → deliverable spec + explicit exit condition (the checkable test the specialist uses to know when they are done) + output path
- Q3 → a "context the specialist won't have" section
- Q4 → constraints, marked as locked
- Q5 → explicit guardrails / "do not" list
- Q6 → the single headline instruction, stated first
- Pick the model per CLAUDE.md (task complexity vs. cost).
Persist durable shared language to memory. Check whether any term from Q3 or decision from Q4 is worth keeping across sessions. Use your assistant's existing memory system — do not create a separate context file. Before writing a memory, apply the filter:
- Would you have to explain this again next session without it?
- Is it genuinely recurring, not specific to this one task?
- Does it already exist in memory or CLAUDE.md?
Only persist entries that pass all three. A shared-language term or locked decision is usually
type: referenceortype: project; keep it tight (name, one-line definition, and Why: for a decision). When in doubt, don't write it.
Then delegate, using the interview answers as the specialist's context.
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.

