Open source · MIT · Free forever
The AI Requirements Toolkit
Two toolkits that make AI do serious analytical work properly — one for requirements engineering, one for Swiss and EU regulatory reporting. Both ship as Claude and Codex skills that run the whole workflow for you. Free, open, and ready to drop into your work.
Pick your toolkit
They share a method and a licence, not an audience. Take the one that matches the work in front of you — or both, they install side by side.
Requirements Engineering Toolkit
Turn vague business requests into clear, testable, traceable requirements — with skills that run the whole workflow for you.
- 5 skills — elicitation, writing, review, test cases, diagrams
- 40+ prompts, patterns, checklists, templates and Mermaid diagrams
- Worked before/after examples you can copy straight into your work
Regulatory Reporting Toolkit
Compare Swiss and EU reporting regimes without an AI quietly inventing the answer — every statement traced to an article, every gap left visible.
- 6 jurisdiction-isolated experts — FMIA 39, FMIA 104, EMIR, MiFIR, MiFID II, FinSA
- Pinpoint citations tagged by how they were obtained
- Conflicts and evidence gaps survive to the executive summary
One idea, two domains
Both toolkits exist because fluent AI output is not the same thing as trustworthy AI output. Neither of them asks you to be more careful — they make the careless answer structurally hard to produce.
Ambiguity is made visible
One toolkit refuses to let “quickly and securely” survive into a requirement. The other refuses to let an unsourced sentence survive into a regulatory brief. Same move, different vocabulary.
A human still decides
Every skill assumes a qualified person makes the final call. The tools accelerate the work and show their reasoning; they do not own the outcome.
Plain Markdown, no lock-in
Every skill, template and checklist is a Markdown file in a public repo. Install the plugin, or copy the one file you need into your own wiki. Both are fine.
MIT, free, forever
No account, no e-mail, no upsell. Use them commercially, fork them, rename them, adapt them to your domain and glossary.
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 toolkits. It costs you a click and means a lot.