メニュー
Start a new OpenSpec change using the artifact workflow. Creates a structured change with proposal, specs, design, and tasks. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement OpenSpec change using Ralph Loop - parallel specialized agents with fresh context per iteration. Use when user wants faster implementation with domain experts working in parallel, or when the change spans multiple domains (backend, frontend, database).
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Archive multiple completed changes at once. Use when the user wants to clean up several completed changes.
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.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
| name | openspec-new-change |
| description | Start a new OpenSpec change using the artifact workflow. Creates a structured change with proposal, specs, design, and tasks. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. |
Start a new change using the artifact-driven OpenSpec approach.
When to Use
Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.
Steps
If no clear input provided, ask what they want to build
Ask the user: "What change do you want to work on? Describe what you want to build or fix."
From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).
IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Validate the change name
user-auth, fix-login-bug, refactor-apiCheck if change already exists
Run: ls -la openspec/changes/ (if directory exists)
If a change with that name exists, suggest continuing it instead of creating new.
Create the change directory
Use the Python kit:
python .agents/openspec_kit.py create "<name>" [schema]
Omit the schema parameter unless the user explicitly requests a different workflow.
This creates a scaffolded change at openspec/changes/<name>/.
Show the artifact status
python .agents/openspec_kit.py status "<name>"
This shows which artifacts need to be created and which are ready.
Get instructions for the first artifact
The first artifact is typically proposal. Get its instructions:
python .agents/openspec_kit.py instructions proposal "<name>"
STOP and wait for user direction
Output
After completing the steps, summarize:
openspec/changes/<name>/)Guardrails