From reqstool
Create or update .reqstool-ai.yaml configuration for a project. Use when the user wants to initialize or reconfigure reqstool-ai settings.
How this skill is triggered — by the user, by Claude, or both
Slash command
/reqstool:initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create or update `.reqstool-ai.yaml` configuration for this project.
Create or update .reqstool-ai.yaml configuration for this project.
Input: None required. Existing config is used as defaults when present.
Steps
Check for existing config
Check if .reqstool-ai.yaml already exists in the project root.
If it exists: read it, show the user the current config, and say
"I found an existing .reqstool-ai.yaml. I'll use it as a starting point —
you can update any values or add/remove modules."
Pre-fill all prompts below with the existing values.
If it does not exist: start fresh with empty/default values.
Gather project-level config
Use AskUserQuestion to collect each value. When updating an existing config, show the current value and ask if the user wants to change it.
my-project"0.1.0"requirements.yml and software_verification_cases.yml.
Default: docs/reqstoolNote: these directories and files do not need to exist yet. The user may be setting up reqstool for the first time.
Gather modules
A module is a subproject that imports a subset of requirements/SVCs from the system level via filters. Projects typically have one or more modules.
If updating: show the existing modules and ask the user which to keep, modify, or remove. Then ask if they want to add new modules.
If new: explain what a module is and ask the user to define their first one.
For each module, collect:
core, app, cli).
This becomes the key in the YAML and is used in commands like
/reqstool:add-req core.core/docs/reqstoolCORE_, CLI_, AUTH_).
All requirement IDs for this module will start with this prefix.
Set to empty string "" for projects using domain-specific prefixes where
IDs are managed manually.SVC_CORE_, SVC_CLI_).
Typically SVC_ followed by the req_prefix.After each module, ask: "Add another module? (yes/no)" Continue until the user says no or indicates they are done.
At least one module is required.
Write the config file
Write .reqstool-ai.yaml to the project root with the collected values.
Use references/reqstool-ai.yaml.template as the template — follow its
structure, comments, and formatting. Replace placeholder values with the
user's inputs and include only the modules the user defined.
Verify (if possible)
If reqstool CLI is installed and the system path contains existing reqstool files,
run reqstool status local -p <system.path> to verify the config.
If reqstool is not installed or files don't exist yet, skip verification and
tell the user they can run /reqstool:status later once their reqstool files are in place.
Report
Show the user:
.reqstool-ai.yaml to version control/reqstool:add-req to add your first requirement,
or /reqstool:status to check traceability status."Guardrails
.reqstool-ai.yaml without reading it first and using it as defaultsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub reqstool/reqstool-ai --plugin reqstool