一键导入
openspec-cli
How to invoke the openspec CLI. Load this BEFORE running any openspec commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
How to invoke the openspec CLI. Load this BEFORE running any openspec commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
How to write specs, name capabilities, and structure requirements. Load this when creating or reviewing proposals, specs, or capability lists.
Principles and patterns for writing agent definitions
Principles and patterns for writing slash command definitions
| name | openspec-cli |
| description | How to invoke the openspec CLI. Load this BEFORE running any openspec commands. |
All openspec CLI commands MUST be prefixed with bunx.
The openspec package is a devDependency — it is not on the system PATH.
# Correct
bunx openspec status
bunx openspec new change "my-change"
# Wrong — will fail
openspec status
openspec new change "my-change"