requirements-intake
Skill1 starsChanged 59 days agoMITView on GitHub
Clarify materially incomplete requests of any kind before planning, using existing project evidence first and bounded structured questions only for remaining decisions.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- EnsoDynamics/enso-methodtheir own version, first seen Nov 1, 2026
- Nashova/LLM-Dev-Frameworktheir own version, first seen Nov 1, 2026
- adam-paterson/skillstheir own version, first seen Oct 11, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- EnsoDynamics/enso-method★ 7same name
- adam-paterson/skills★ 1same name
- Nashova/LLM-Dev-Framework★ 0same 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 repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- content-safetySkill
- context-compactionSkill
- coordinator-communicationSkill
- cortex-controlSkill
- design-frontend-designSkill
- design-impeccableSkill
- design-reference-analysisSkill
- design-ui-ux-pro-maxSkill
- design-visual-qaSkill
- design-workflowSkill
- documentation-syncSkill
- knowledge-harvest-scopeSkill
- knowledge-harvestSkill
- orchestratorSkill
- skill-authoringSkill
- skill-managementSkill
- tool-disciplineSkill
- tool-discipline-workerSkill
- worker-accessibility-auditorSkill
- worker-accessibility-fixerSkill
- worker-architectSkill
- worker-backend-devSkill
- worker-build-verificationSkill
- worker-code-reviewerSkill
- worker-database-architectSkill
- worker-data-engineerSkill
- worker-debuggerSkill
- worker-devops-engineerSkill
- worker-explorerSkill
- worker-frontend-devSkill
- worker-fullstack-devSkill
- worker-generalSkill
- worker-mobile-devSkill
- worker-performance-engineerSkill
- worker-plannerSkill
- worker-qa-engineerSkill
- worker-refactorerSkill
- worker-security-auditorSkill
- worker-senior-consultantSkill
- worker-technical-writerSkill
- worker-ux-designerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 8
Use before planning a new request whose goal lacks information that would materially change the result.
- Distinctive: line 10
Do not interrogate the user when the request and project evidence suffice.
- Distinctive: line 14
Read the request, retained answers, project instructions and relevant product docs.
- Distinctive: line 24
Never ask what docs, code or a retained answer already establish.
- Distinctive: line 26
Read linked package references through Cortex read_skill using question-banks or agreed-spec (also accepted in references/<id>.md form), …
- Distinctive: line 43
Ask at most two rounds, normally one, with at most five material questions per round (or fewer if the live schema requires it).
- Distinctive: line 46
If a critical decision is still unresolved after the bound, do not guess or implement it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Requirements intake
Use before planning a new request whose goal lacks information that would materially change the result. Apply to every request kind, not just design. Do not interrogate the user when the request and project evidence suffice.
Check sufficiency first
Read the request, retained answers, project instructions and relevant product docs. Use bounded code-index orientation for existing behavior and constraints; do not turn intake into a coordinator implementation investigation. If locating facts needs substantial investigation, propose that bounded investigation rather than asking the user to reconstruct the repository.
Separate established facts, decisions the user must make, and safe implementation details delegated to a specialist. Check goal, affected users, scope and non-goals, observable acceptance, constraints, risks, and verification. Missing information matters only if different answers would change scope, behavior, risk or acceptance. Never ask what docs, code or a retained answer already establish.
Read linked package references through Cortex read_skill using question-banks
or agreed-spec (also accepted in references/<id>.md form), not project_read on
the target project.
Ask only material gaps
- Select only relevant prompts from the question banks. For feature/product ask outcome and users; for bug/incident ask expected versus actual behavior and reproduction; for refactor ask invariants and permitted changes; for UI/UX ask audience, platforms, screens and visual direction; for documentation ask audience and authoritative facts; for infra/ops ask target, authority and rollback; for investigation ask the decision and evidence needed.
- Group related questions into one request through the advertised coordinator question tool. Read its live schema; do not use a native engine question tool or prose-only questions. Use the runtime-selected user question language. Offer meaningful, distinct options grounded in the project, explain tradeoffs, and preserve custom free text. Do not present invented requirements as defaults.
- Ask at most two rounds, normally one, with at most five material questions per round (or fewer if the live schema requires it). End the turn immediately after asking. On resumption, incorporate real answers and ask only remaining gaps.
- If a critical decision is still unresolved after the bound, do not guess or implement it. Offer a bounded discovery-only scope with no product commitment, or report the concrete missing decision and stop the implementation proposal. A user explicitly delegating a choice is a decision; label the resulting specialist proposal rather than inventing functionality.
Carry the agreement forward
Record the agreed specification in plan objectives: goal, users, scope/non-goals, acceptance examples, constraints, risks, verification expectations and unresolved items. Preserve exact source references for consequential decisions. Use the spec outline as a completeness check, not a mandate to create a document for every small fix.
For durable product or design intake, propose a writing assignment to record the agreed facts in the target project's documentation before dependent work. Read-only designers return specifications in reports; writers persist them. Do not modify lifecycle, permissions or question contracts, promise a tool capability not observed in this session, or treat answered intake as runtime acceptance.
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.

