메뉴
Start a new change using the experimental artifact workflow (OPSX)
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | opsx-new |
| description | Start a new change using the experimental artifact workflow (OPSX) |
| metadata | {"category":"Workflow","tags":["workflow","artifacts","experimental"]} |
Start a new change using the experimental artifact-driven approach.
Input: The argument after /opsx-new is the change name (kebab-case), OR a description of what the user wants to build.
Steps
If no 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.
Load architectural context
Before creating the change, silently read all applicable ADRs. These inform what is architecturally possible and constrain the proposal scope.
| Location | What | When |
|---|---|---|
openspec/changes/<name>/context-brief.md | Specter intelligence brief — features, stories, stakeholders, schemas | If present — this is the primary input |
openspec/architecture/adr-*.md | Repo-specific ADRs (data model, workflows, security) | Always check |
../../../openspec/architecture/adr-*.md (relative to skill base dir) | Company-wide ADRs (17 Conduction-wide decisions) — these live in the Hydra repo that contains this skill | Always load |
docs/ARCHITECTURE.md | App-specific technology decisions | If present |
docs/FEATURES.md | Feature tiers and roadmap phases | If present |
Read these silently — do not list them to the user. If a context-brief.md exists for this change, it contains market-researched intelligence data. Use it as the primary source for the change description — do not ask the user what to build when the brief already describes it.
Use them to inform the change name validation (e.g., if the user asks for something that contradicts an ADR, flag it).
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. 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.
Ask how to proceed
After showing the status and first artifact template, use AskUserQuestion to ask:
"Change
<name>is ready. How would you like to proceed?"
Options:
/opsx-ff <name>) — fastest path to implementation; I'll create proposal, specs, design, and tasks in one go/opsx-continue <name>) — more control; you review and approve each artifact before the next/opsx-explore) — explore ideas, constraints, and approach before committing to a direction/opsx-continue <name>Output
After completing the steps, summarize:
Guardrails
/opsx-continue insteadReset the OpenRegister development environment (stop, remove volumes, restart, install apps)
Create a Pull Request from the current branch — runs local checks, picks target branch, and opens the PR on GitHub
Analyze a project's OpenSpec from 8 persona perspectives and suggest additional features
Detect admin settings Vue components registered in the vue-router. Admin settings are rendered by Nextcloud's settings framework via `AdminSettings.php`; adding their Vue components to the in-app router exposes them as publicly-accessible frontend routes, bypassing all server-side access checks. ADR-004 hard rule. Observed 2026-04-30 on doriath where `/settings → AdminRoot` was a route in `src/router/index.js` (commit c7c72e9).
Run `composer audit` to check composer.lock dependencies for known CVEs. Invoked by the builder before push and the reviewer's mandatory block. Mirrors the orchestrator's `composer-audit` quality gate.
Scan lib/ for forbidden debug helpers (var_dump / die / error_log / print_r / dd / dump) that should not ship. Invoked by the builder before push, by the reviewer as Mandatory Step 2, and by the fixer during a retry. Mirrors the orchestrator's `forbidden-patterns` quality gate.