Stats
Links
Categories
Reqstool AI Integration
AI-assisted management of reqstool requirements traceability, with optional OpenSpec integration.
Provides config-driven skills and commands that let AI coding assistants help you manage requirements, verification cases, and traceability filters. Works with both Claude Code and GitHub Copilot CLI — same plugin, same format.
Quick start
Claude Code
# Add marketplace (one-time)
/plugin marketplace add reqstool/reqstool-ai
# Install core plugin
/plugin install reqstool@reqstool-ai --scope project
# Optional: OpenSpec integration
/plugin install reqstool-openspec@reqstool-ai --scope project
GitHub Copilot CLI
# Add marketplace (one-time)
copilot plugin marketplace add reqstool/reqstool-ai
# Install core plugin
copilot plugin install reqstool@reqstool-ai
# Optional: OpenSpec integration
copilot plugin install reqstool-openspec@reqstool-ai
Configure your project
After installing the plugin, run /reqstool:init to create .reqstool-ai.yaml in your project root:
/reqstool:init
This walks you through setting up:
- URN — your project identifier used in reqstool YAML files
- Revision — version string for new requirements and SVCs
- System path — where the system-level requirements and SVCs live
- Modules — one or more subproject modules with their paths and ID prefixes
You can re-run /reqstool:init at any time to update the config (e.g., to add new modules). It reads the existing .reqstool-ai.yaml and uses current values as defaults.
Configuration (.reqstool-ai.yaml)
All reqstool skills and commands read .reqstool-ai.yaml from the project root. This file defines your project's reqstool structure:
# Project URN — matches the urn in your reqstool YAML files
urn: my-project
# Revision string for new requirements and SVCs
revision: "0.1.0"
# System-level reqstool directory (SSOT for requirements and SVCs)
system:
path: docs/reqstool
# Subproject modules — each imports a subset of requirements/SVCs via filters
modules:
core:
path: core/docs/reqstool
req_prefix: CORE_ # Requirement IDs: CORE_0001, CORE_0002, ...
svc_prefix: SVC_CORE_ # SVC IDs: SVC_CORE_0001, SVC_CORE_0002, ...
app:
path: app/docs/reqstool
req_prefix: CLI_
svc_prefix: SVC_CLI_
| Field | Description |
|---|---|
urn | Project URN used in reqstool YAML files and filter keys |
revision | Version string stamped on new requirements and SVCs |
system.path | Path to the system-level reqstool directory (SSOT) |
modules.<name>.path | Path to a subproject's reqstool directory (contains filter files) |
modules.<name>.req_prefix | Requirement ID prefix (e.g., CORE_). Set to "" for domain-specific prefixes |
modules.<name>.svc_prefix | SVC ID prefix (e.g., SVC_CORE_) |
Skills and commands
Commands (user-invoked)
| Command | Description |
|---|---|
/reqstool:init | Create or update .reqstool-ai.yaml configuration interactively |
/reqstool:add-req | Add a new requirement and update subproject filters |
/reqstool:add-svc | Add a new Software Verification Case and update filters |
/reqstool:status | Show requirements traceability status for system or a module |
Skills (auto-applied)
| When you're... | Skill |
|---|---|
| Working with reqstool YAML files or annotations | reqstool-conventions |
Skills are applied automatically based on context — no manual invocation needed.
reqstool-openspec plugin (separate install)
| When you're... | Skill |
|---|---|
| Working with OpenSpec spec.md files | reqstool-openspec |
Command details
/reqstool:init
Interactively create or update .reqstool-ai.yaml in your project root. Walks you through URN, revision, system path, and module definitions (name, path, ID prefixes). When re-run on a project that already has a config, it reads existing values as defaults so you can add modules or change settings without starting over.