원클릭으로
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"