メニュー
Install OpenSpec CLI (if not already installed) and run openspec init --tools claude to add spec-driven development skills to this project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Record an architecture/design decision as an ADR (Architecture Decision Record) in the target repository's docs/adr/. Use when the user wants to document a design decision, its alternatives and consequences, or says "record this decision" / "write an ADR".
Generate a self-contained HTML manual-testing guide for an implemented change — environment setup, a visual test-flow diagram, step-by-step scenarios with expected results, and interactive pass/fail checkboxes with a Markdown results export. Use when the user wants to verify an implementation by hand, asks "how do I test this", or wants a verification document for a feature/branch/PR.
Generate a self-contained HTML onboarding tour of a repository — architecture diagram, directory map, key flow walkthroughs, and a recommended reading order — for new team members. Use when the user wants onboarding material, asks for a codebase overview/architecture tour, or wants to explain a repo to someone new.
Generate a self-contained HTML code-review guide for the current changes — big-picture overview, architecture diagram of affected modules, a file/class responsibility map, and an annotated change walkthrough — so a reviewer can grasp the whole implementation before diving into the diff. Use when the user wants review material for a branch/PR, asks to "explain the changes for review", or wants a visual summary of what was implemented where.
Investigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".
Capture a reusable, non-obvious project insight into the rules home where it will auto-inject in future sessions. Use when investigation or implementation surfaces knowledge worth persisting (a gotcha, a convention, the "why" behind a decision), or when the user asks to remember a project learning.
| name | setup-openspec |
| description | Install OpenSpec CLI (if not already installed) and run openspec init --tools claude to add spec-driven development skills to this project. |
| disable-model-invocation | true |
| allowed-tools | Bash(node --version) Bash(npm list *) Bash(npm install *) Bash(openspec *) |
Set up OpenSpec for spec-driven development in this project.
Steps:
Verify Node.js ≥ 20.19.0 is available. Run node --version. If Node is missing or older than 20.19.0, stop and tell the user to upgrade Node.js first.
Check whether the OpenSpec CLI is already installed globally:
npm list -g @fission-ai/openspec --depth=0
If it is not installed (command exits non-zero or output does not mention @fission-ai/openspec), install it:
npm install -g @fission-ai/openspec@latest
Run OpenSpec initialization in the current project directory:
openspec init --tools claude
Report what was done:
openspec init --tools claude/opsx:explore, /opsx:propose, /opsx:apply, /opsx:archive)