en un clic
openspec-new
Start a new OpenSpec change with artifact workflow
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Menu
Start a new OpenSpec change with artifact workflow
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Save current session state to a handover document for seamless continuation in a new session. Invoke manually or triggered automatically when context window reaches 85%.
Use when the user wants to delegate a task to OpenAI Codex CLI, get a second opinion, or run codex review on changes
Configurable 9-phase feature development workflow enforcer (Phase 0 Context Setup → Phase 8 Approval & Commit). Delegates planning to OpenSpec (proposal→specs→design→tasks) and enhances execution with superpowers skills (TDD, subagent-driven-development, worktrees, verification). Auto-validates phase transitions, manages state via context.md, and orchestrates specialized agents. Use when user says "start feature" or "resume feature", mentions implementing/building/creating a feature, needs structured development process, references TDD or test-driven development, asks about feature planning or implementation phases, references 9-phase workflow or mentions "Phase 1" or "Planning phase", needs approval gates or phase validation, or asks "how do I start a feature" or "what's the development workflow".
Structured E2E test troubleshooting using the 6-layer diagnostic ladder (Frontend → API → SP/Schema → Infra → CI/CD). Use when any E2E test fails, UI doesn't render, auth drops, unexpected status codes, CI passes locally but fails in pipeline, or any test failure where the root cause is unclear. Routes to the correct read-only diagnostic agent based on the symptom, walks the sequential ladder with [EVIDENCE]/[HANDOFF]/[ROOT-CAUSE] taxonomy, and enforces the Fix Gate (no action before root cause confirmed).
Post-session retrospective — append tagged learnings (with severity) to configured learnings file (default: `learnings.md`)
| name | openspec-new |
| description | Start a new OpenSpec change with artifact workflow |
| license | MIT |
| compatibility | Requires openspec CLI. |
| metadata | {"author":"openspec","version":"1.0","generatedBy":"Spectra"} |
Start a new change using the experimental artifact-driven approach.
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
Use the AskUserQuestion tool (open-ended, no preset options) to ask:
"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.
Determine the workflow schema
Use the default schema (omit --schema) unless the user explicitly requests a different workflow.
Use a different schema only if the user mentions:
--schema <name>openspec schemas --json and let them chooseOtherwise: Omit --schema to use the default.
Create the change directory
openspec new change "<name>"
Add --schema <name> only if the user requested a specific workflow.
This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.
Show the artifact status
openspec status --change "<name>"
This shows which artifacts need to be created and which are ready (dependencies satisfied).
Get instructions for the first artifact
The first artifact depends on the schema (e.g., proposal for spec-driven).
Check the status output to find the first artifact with status "ready".
openspec instructions <first-artifact-id> --change "<name>"
This outputs the template and context for creating the first artifact.
STOP and wait for user direction
Output
After completing the steps, summarize:
Guardrails