
Open source · MIT · Free forever
The AI Requirements Toolkit
The checklists, prompts, patterns, templates and diagrams I reach for to turn vague requirements into clear, testable ones — now with Claude/Codex Skills that run the whole workflow for you. Free, open, and ready to drop into your work.
★ New — Claude/Codex Skills
The toolkit that runs itself
Copying prompts and filling templates is good. Having Claude or Codex do the work is better. Drop these Skills into Claude or Codex and it runs the whole workflow for you — asking the right questions, applying the method, shaping the output with the bundled templates, and self-checking against the bundled checklists. Five skills, one for every stage of the requirements lifecycle, that hand off to each other from first request to final test.
- 1requirements-startA thin business request arrives — it frames the problem, maps stakeholders, and plans your discovery or validation workshop.
- 2requirements-writerDrafts testable, traceable requirements, INVEST user stories, Given/When/Then criteria and measurable NFRs — with battle-tested feature patterns.
- 3requirements-reviewerAudits existing requirements for ambiguity, risk, gaps and readiness, and classifies every finding by severity.
- 4requirements-test-casesTurns acceptance criteria into executable test cases and a traceability matrix, so nothing ships untested.
- 5requirements-diagramsGenerates tailored Mermaid diagrams — context, use case, lifecycle, sequence, traceability — ready to drop into a spec.
›/plugin marketplace add clarityisrare/ai-requirements-toolkit›/plugin install requirements-toolkit@ai-requirements-toolkitAdds this repo as a plugin marketplace, then installs all five skills. Update later with /plugin marketplace update ai-requirements-toolkit.
›/plugin marketplace add clarityisrare/ai-requirements-toolkit›/plugin install requirements-toolkit›/reload-pluginsIn Codex, install the GitHub plugin first — it's what resolves the marketplace from GitHub — then run the commands above.
The one move it's built around
Most requirements aren't missing — they're vague, and everyone reads them differently. The whole toolkit pushes in one direction: making that vagueness impossible.
Before
“The system should let users upload documents quickly and securely.”
After
“The system shall allow authenticated customers to upload PDF files up to 20 MB, virus-scanned before they become available and visible only to the customer and reviewers in the owning department.”
What's inside
Five Claude/Codex Skills plus 40+ plain-Markdown and Mermaid files across seven folders — run a skill, or copy a file and adapt the wording. Your choice.
Skills
5 filesClaude/Codex Skills that run each workflow for you — elicitation, writing, review, test cases and diagrams, across the whole lifecycle.
Patterns
9 filesReusable requirement patterns for common features — uploads, notifications, approvals, access control, search, export, integrations, audit trails.
Prompts
9 filesCopy-paste AI prompts: acceptance criteria, user stories, NFRs, test cases, ambiguity detection, review and elicitation.
Checklists
6 filesFast pass/fail reviews for requirements, user stories, NFRs, readiness, security & privacy, and AI output.
Templates
8 filesFill-in-the-blank starting points: requirement, NFR, contract, stakeholder analysis, glossary, decision record, risk register.
Diagrams
6 filesMermaid sources you can drop straight into a spec — context, use case, approval, lifecycle, sequence and traceability.
Examples
7 filesWorked, before/after walkthroughs that show the tools in action — including what the AI review prompts actually return.
How to use it
- Browse by task. Writing criteria? Start in prompts. Reviewing someone else's work? Start in checklists.
- Copy, don't depend. Take what's useful into your own repo or wiki and adapt it to your domain and glossary.
- Keep a human in the loop. The AI prompts and checklists assume a person makes the final call — the tools accelerate the work, they don't own it.
If it saves you time, star it
A star is the signal that keeps this growing — it tells me which pieces are worth expanding, and it helps other people find the toolkit. It costs you a click and means a lot.
