From reqstool
Run reqstool traceability status on the local filesystem. Use when the user wants to check requirement coverage, missing implementations, or test status.
How this skill is triggered — by the user, by Claude, or both
Slash command
/reqstool:statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run `reqstool status local` for a reqstool directory in this project.
Run reqstool status local for a reqstool directory in this project.
Input: Optional module name from .reqstool-ai.yaml. Defaults to system-level.
Configuration
Read .reqstool-ai.yaml — see reqstool-conventions.md for field reference.
Steps
Read config
Read .reqstool-ai.yaml. Build a mapping of module names to their paths.
Determine which path to use
core), use that module's path from .reqstool-ai.yaml.system.path).Run reqstool status
reqstool status local -p <path>
Show the output directly — reqstool traverses imports and implementation configuration automatically, so no further summarization is needed.
If reqstool is not installed
If the command fails with "not found", tell the user:
reqstool is not installed. Install with: pipx install reqstool
Guardrails
npx claudepluginhub reqstool/reqstool-ai --plugin reqstoolCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.