From reqstool-openspec
OpenSpec + reqstool integration conventions. Auto-applied when working with OpenSpec spec.md files that reference reqstool requirement or SVC IDs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/reqstool-openspec:reqstool-openspecThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
When creating or modifying OpenSpec spec.md files that reference reqstool requirements or SVCs,
When creating or modifying OpenSpec spec.md files that reference reqstool requirements or SVCs, read the convention files from this skill's references/ directory.
references/reqstool-openspec-conventions.md — how to reference reqstool IDs in spec.md files, format rules, validationreferences/config-rules.yaml — reqstool rules to add to openspec/config.yamlnpx claudepluginhub reqstool/reqstool-ai --plugin reqstool-openspecWrite and manage spec files with search, conflict detection, and reporting. Use when user asks to create a spec, update a spec, write a spec, or mentions 스펙 생성, 스펙 업데이트, 스펙 작성, 스펙 만들어줘. Proactively trigger whenever the user's request involves specification documents, even if they don't explicitly say "spec".
Provides conventions for writing self-contained, implementation-ready spec documents. Distinguishes specs from docs; covers structure including data model, architecture, security, operations, scope, and deliverables.