requirements-review
Skill1 starsChanged 3 months agoMITView on GitHub
Review requirements before implementation by turning fuzzy intent into decisions, constraints, risks, and a first executable step. Use when the user asks to clarify scope, review requirements, resolve ambiguity, identify constraints, or use align-change.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- mryo0826/aidd-practice-guidetheir own version, first seen Nov 15, 2026
- AndersonAndrad/skillstheir own version, first seen Nov 8, 2026
- frnkgns/Overgeared-Skillstheir own version, first seen Nov 8, 2026
- tusharranjan-ai/testronauttheir own version, first seen Oct 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- frnkgns/Overgeared-Skills★ 7same name
- mryo0826/aidd-practice-guide★ 5same name
- tusharranjan-ai/testronaut★ 2same name
- AndersonAndrad/skills★ 1same 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- debugSkill
- domain-modelingSkill
- handoffSkill
- implementation-planSkill
- test-and-verifySkill
- webgl-scroll-siteSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
12
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 12
Do one job: turn unclear intent into the next executable step.
- Distinctive: line 15
Do not hide capability gaps.
- Distinctive: line 16
Stop discovery when the entry point and first proof are clear.
- Distinctive: line 20
Use for feature ideas, refactors, product decisions, workflow changes, migrations, and plans that are not yet concrete enough to edit …
- Distinctive: line 24
Do not use when the request is already a clear edit, a failing command, a review, or a pure explanation.
- Distinctive: line 28
Read the current repo or config surface that will be changed.
- Distinctive: line 30
Ask only the decisions that block a safe first step.
- Distinctive: line 31
If enough context exists, choose conservative defaults and state them.
- Distinctive: line 36
Prefer repo truth over stale docs.
- Distinctive: line 37
Prefer the smallest user-visible behavior that can be verified end to end.
- Distinctive: line 38
Prefer preserving existing interfaces unless the interface is the problem.
- Distinctive: line 51
If the user asked for execution, continue into the first step after the review.
“Common” is measured: kept by at least 6 in 10 of the 3 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
requirements-review
Resolve ambiguity quickly enough that implementation can start.
Unix/Pi Contract
- Do one job: turn unclear intent into the next executable step.
- Consume repo facts and user intent; emit decisions, blockers, next step, and proof command.
- Stay terse. Ask only the question that changes the next action.
- Do not hide capability gaps. If evidence, tools, credentials, or runtime access are missing, say exactly what is missing.
- Stop discovery when the entry point and first proof are clear.
Use
Use for feature ideas, refactors, product decisions, workflow changes, migrations, and plans that are not yet concrete enough to edit safely.
Do Not Use
Do not use when the request is already a clear edit, a failing command, a review, or a pure explanation.
Workflow
- Read the current repo or config surface that will be changed.
- Extract the user goal, non-goals, constraints, existing contracts, likely risks, and missing choices.
- Ask only the decisions that block a safe first step. Prefer one concise question over a broad interview.
- If enough context exists, choose conservative defaults and state them.
- End with a first executable step and the verification command that proves it.
Decision Quality
- Prefer repo truth over stale docs.
- Prefer the smallest user-visible behavior that can be verified end to end.
- Prefer preserving existing interfaces unless the interface is the problem.
- Name irreversible, external, security, or data-loss risks explicitly.
Output
Return:
- Goal in one sentence.
- Decisions already resolved.
- Open blocker, if any.
- First step to implement.
- Verification command.
If the user asked for execution, continue into the first step after the review.
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.

