Reqstool Ai
- Updated July 21, 2026
- reqstool/reqstool-ai
reqstool-ai is a Claude Code and Copilot CLI marketplace with two plugins that manage reqstool requirements YAML, verification cases, and traceability filters for developers practicing requirements-driven development.
About
reqstool-ai is a plugin marketplace for AI-assisted reqstool traceability. The core reqstool plugin adds /reqstool:init to generate .reqstool-ai.yaml, /reqstool:add-req and /reqstool:add-svc for system-level requirements and Software Verification Cases, and /reqstool:status for traceability reports via MCP or CLI fallback. Auto-applied reqstool-conventions skills bundle overview, annotation, decomposition, and build-config reference docs for Java, Python, and TypeScript @Requirements and @SVCs placement. A separate reqstool-openspec plugin links OpenSpec spec.md files to reqstool IDs. The reqstool MCP server (reqstool ≥ 0.10.0) exposes get_status, list_requirements, and related structured tools configured through .mcp.json. Prerequisites include pipx-installed reqstool CLI and optional OpenSpec. Install with /plugin marketplace add reqstool/reqstool-ai and /plugin install reqstool@reqstool-ai --scope project. Use reqstool-ai when Claude sessions must keep requirements.yml, software_verification_cases.yml, and module filters consistent.
- Ships 2 plugins: reqstool core and optional reqstool-openspec integration
- Four commands: init, add-req, add-svc, and status with MCP or CLI fallback
- Auto-applies reqstool-conventions skills for Java, Python, TypeScript annotations
- Config-driven .reqstool-ai.yaml defines URN, revision, system path, modules
- Integrates reqstool MCP server get_status when .mcp.json is configured
Reqstool Ai by the numbers
- Data as of Jul 22, 2026 (Skillselion catalog sync)
/plugin marketplace add reqstool/reqstool-aiAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | July 21, 2026 |
|---|---|
| Repository | reqstool/reqstool-ai ↗ |
How do you manage reqstool traceability from Claude Code?
Run /reqstool:add-req in Claude Code to append a requirement to system requirements.yml and update module filter files from .reqstool-ai.yaml prefixes.
Who is it for?
Teams using reqstool SSOT YAML with modular prefixes who want Claude or Copilot CLI to add requirements, SVCs, and status checks without manual ID bookkeeping.
Skip if: Projects without reqstool CLI installed, teams not using requirements.yml traceability, or workflows that do not annotate code with @Requirements or @SVCs.
What you get
.reqstool-ai.yaml config, updated requirements.yml and SVC YAML, module filter files, and traceability status reports.
- .reqstool-ai.yaml
- Updated requirements and SVC YAML
- Traceability status report
By the numbers
- Marketplace bundles 2 plugins: reqstool and reqstool-openspec
- Exposes 4 slash commands: init, add-req, add-svc, and status
- Requires reqstool CLI ≥ 0.10.0 for MCP server integration
Plugins in this marketplace
2 plugins - install individually after you add the marketplace.
Recommended Marketplaces
How it compares
Pick reqstool-ai over ad-hoc spec markdown when traceability must stay in reqstool YAML with module filters, SVC mirroring, and MCP-backed status checks.
FAQ
How many plugins does Reqstool Ai marketplace include?
Reqstool Ai ships two plugins: reqstool for core traceability commands and conventions, and reqstool-openspec for OpenSpec spec.md integration. Install the core plugin with /plugin install reqstool@Reqstool Ai and OpenSpec support separately.
What does /reqstool:init create?
Reqstool Ai /reqstool:init interactively writes .Reqstool Ai.yaml at the project root with URN, revision, system.path SSOT directory, and per-module paths plus req_prefix and svc_prefix values used by add-req and add-svc.
Does reqstool:status require the MCP server?
Reqstool Ai prefers the reqstool MCP server get_status tool when .mcp.json configures reqstool mcp, but automatically falls back to reqstool status local CLI and notifies you when MCP is unavailable.