requirements-authoring
Skill2 starsChanged 3 months agoMITView on GitHub
Draft functional requirements from a single OpenAPI endpoint. One invocation per endpoint.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cypher0n3/dotagentstheir own version, first seen Nov 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- cypher0n3/dotagents★ 3same 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 repository3 other files it gives its agents.
- requirements-reviewSkill
- test-case-reviewSkill
- test-designSkill
The file
Files
Requirements Authoring
Draft functional requirements (FRs) for exactly one OpenAPI endpoint.
A requirement states what the API must do, in behaviour terms. It is not a
test. "The API returns 400 when name is missing" is a requirement; "send a
POST without name and assert 400" is a test case, and belongs to a later stage.
Input
Endpoint detail (method, path, operationId, summary, description, parameters, requestBody, responses, security), the coverage categories selected for this run, and the OPTOKEN to build IDs from.
Rules
- Produce 1–5 requirements. Cover only the categories requested for this run.
- Each requirement is independently checkable. If you cannot say how you would know it holds, it is prose — rewrite it.
- Ground every requirement in the spec. Never assert a status code, field or error shape the spec does not declare for this operation. A requirement the spec does not support is worse than a missing one.
acceptance_criteriacarries the checkable statements, one per entry. Do not bury them indescription.spec_sourceis a JSON pointer to what the requirement derives from, e.g.#/paths/~1pet/post/requestBody.- Skip categories that do not apply: no
authrequirements for an endpoint that declares no security, noboundaryrequirements where nothing has bounds. - Priority: P1 for the operation's core contract, P2 for standard validation, P3 for edge conditions.
Category guidance
- happy_path — valid request, declared success response.
- negative — missing required input, wrong type, malformed payload.
- boundary — min/max length, numeric limits, empty collections, absent optionals.
- auth — missing, expired, or insufficient credentials. Only if security is declared.
- security — injection probes, IDOR, mass assignment. Only where the shape allows it.
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.

