added skills, fixes

codex

---

name: openspec-apply-change

description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

allowed-tools: Bash(openspec:*)

license: MIT

compatibility: Requires openspec CLI.

metadata:

  author: openspec

  version: "1.0"

  generatedBy: "1.8.0"

---

Implement tasks from an OpenSpec change.

**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.

**Input**: Optionally specify a change name (e.g., `$openspec-apply-change (Codex) or /openspec-apply-change (other agents) add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

**Steps**

1. **Select the change**

   If a name is provided, use it. Otherwise:

   - Infer from conversation context if the user mentioned a change

   - Auto-select if only one active change exists

   - If ambiguous, run `openspec list --json` to get available changes and ask the user to select one

   Always announce: "Using change: <name>" and how to override (e.g., `$openspec-apply-change (Codex) or /openspec-apply-change (other agents) <other>`).

2. **Check status to understand the schema**

   ```bash

   openspec status --change "<name>" --json

   ```

   Parse the JSON to understand:

   - `schemaName`: The workflow being used (e.g., "spec-driven")

   - `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints

   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)

3. **Get apply instructions**

   ```bash

   openspec instructions apply --change "<name>" --json

   ```

   This returns:

   - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)

   - Progress (total, complete, remaining)

   - Task list with status

   - Dynamic instruction based on current state

   - Optional `context`: current required project instruction input from the selected root

   - Optional `operationGuidance`: current advisory guidance for apply

   **Handle states:**

   - If `state: "blocked"` (missing artifacts): show message, suggest using `$openspec-continue-change (Codex) or /openspec-continue-change (other agents)` (if it is not installed, run `openspec status --change "<name>" --json` to see the next artifact and `openspec instructions <artifact-id> --change "<name>" --json` for how to create it)

   - If `state: "all_done"`: congratulate, suggest archive

   - Otherwise: proceed to implementation

   Treat `context` as a required prompt-level input. Read and consider it, and

   apply relevant project facts, conventions, and constraints while implementing.

   Treat `operationGuidance` as optional additive advice. Read and consider every

   entry, and follow entries that are applicable and compatible with the built-in

   workflow.

   Keep both fields separate from CLI-returned state, missing artifacts, tasks,

   progress, `contextFiles`, and the built-in `instruction`. They are not

   evidence of task completion, do not replace the built-in instruction, and do

   not permit bypassing a blocked state. If context conflicts with the built-in

   instruction, an explicit user choice, or a CLI-controlled value, report the

   conflict and preserve the controlling value. If guidance is inapplicable or

   conflicts with those controlling inputs, do not follow it and explain why.

   These are prompt-level behavior contracts, not enforceable checks.

4. **Read context files**

   Read every file path listed under `contextFiles` from the apply instructions output.

   The files depend on the schema being used:

   - **spec-driven**: proposal, specs, design, tasks

   - Other schemas: follow the contextFiles from CLI output

   Do not copy `context` or `operationGuidance` verbatim into implementation

   files or planning artifacts unless the user separately asks for that content.

5. **Show current progress**

   Display:

   - Schema being used

   - Progress: "N/M tasks complete"

   - Remaining tasks overview

   - Dynamic instruction from CLI

6. **Implement tasks (loop until done or blocked)**

   For each pending task:

   - Show which task is being worked on

   - Make the code changes required

   - Keep changes minimal and focused

   - Mark task complete in the tasks file: `- [ ]` → `- [x]`

   - Continue to next task

   **Pause if:**

   - Task is unclear → ask for clarification

   - Implementation reveals a design issue → suggest updating artifacts

   - Error or blocker encountered → report and wait for guidance

   - User interrupts

7. **On completion or pause, show status**

   Display:

   - Tasks completed this session

   - Overall progress: "N/M tasks complete"

   - If all done: suggest archive

   - If paused: explain why and wait for guidance

**Output During Implementation**

```

## Implementing: <change-name> (schema: <schema-name>)

Working on task 3/7: <task description>

[...implementation happening...]

✓ Task complete

Working on task 4/7: <task description>

[...implementation happening...]

✓ Task complete

```

**Output On Completion**

```

## Implementation Complete

**Change:** <change-name>

**Schema:** <schema-name>

**Progress:** 7/7 tasks complete ✓

### Completed This Session

- [x] Task 1

- [x] Task 2

...

All tasks complete! You can archive this change with `$openspec-archive-change (Codex) or /openspec-archive-change (other agents)`.

```

**Output On Pause (Issue Encountered)**

```

## Implementation Paused

**Change:** <change-name>

**Schema:** <schema-name>

**Progress:** 4/7 tasks complete

### Issue Encountered

<description of the issue>

**Options:**

1. <option 1>

2. <option 2>

3. Other approach

What would you like to do?

```

**Guardrails**

- Keep going through tasks until done or blocked

- Always read context files before starting (from the apply instructions output)

- If task is ambiguous, pause and ask before implementing

- If implementation reveals issues, pause and suggest artifact updates

- Keep code changes minimal and scoped to each task

- Update task checkbox immediately after completing each task

- Pause on errors, blockers, or unclear requirements - don't guess

- Use contextFiles from CLI output, don't assume specific file names

- Do not use context or operation guidance as proof that a task is complete

- Apply relevant project context; report conflicts with controlling workflow inputs

- Consider every guidance entry; explain any inapplicable or conflicting advice

- Do not copy runtime context or operation guidance into implementation files or planning artifacts

- Preserve CLI-controlled blocked/ready/all-done behavior and completion criteria

**Fluid Workflow Integration**

This skill supports the "actions on a change" model:

- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions

- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

---

name: openspec-archive-change

description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

allowed-tools: Bash(openspec:*)

license: MIT

compatibility: Requires openspec CLI.

metadata:

  author: openspec

  version: "1.0"

  generatedBy: "1.8.0"

---

Archive a completed change in the experimental workflow.

**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.

`<capability-path>` is the spec directory relative to `specs/` (for example, `user-auth` or `identity/user-auth`). Preserve the full path from each delta spec when resolving its main spec.

**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

**Steps**

1. **Select the change**

   If a name is provided, use it. Otherwise:

   - Infer from conversation context if the user mentioned a change

   - Auto-select if only one active change exists

   - If ambiguous, run `openspec list --json` to get available changes and ask the user to select one

   When prompting, show only active changes (not already archived).

   Include the schema used for each change if available.

   Always announce: "Using change: <name>" and how to override (e.g., `$openspec-archive-change (Codex) or /openspec-archive-change (other agents) <other>`).

   **Load current archive inputs before the existing archive checks:**

   After resolving the selected change and planning root, run:

   ```bash

   openspec instructions archive --change "<name>" --json

   ```

   Keep the same selected-root flags on this command. This lookup is advisory and

   optional: it only supplies extra prompt inputs, so it must never block archiving.

   If it exits non-zero or returns invalid JSON — for example on an older CLI that

   does not support this command yet — continue the archive workflow with no

   context and no operation guidance. Do not report an error and do not stop.

   A successful response may omit both optional fields. Treat `context` as a

   required prompt-level input: read and consider it, and apply relevant project

   facts, conventions, and constraints. Treat `operationGuidance` as optional

   additive advice: read and consider every entry, and follow entries that are

   applicable and compatible with the built-in archive workflow.

   Keep both fields separate from built-in steps, explicit user choices, resolved

   paths, CLI checks, and command contracts. If context conflicts with one of those

   controlling inputs, report the conflict and preserve the controlling value. If

   guidance is inapplicable or conflicts with a controlling input, do not follow it

   and explain why. Do not infer replacement paths, skipped prompts, or flags from

   either field, and do not copy their text verbatim into specs, change artifacts,

   or archive summaries unless the user separately asks for it. These are

   prompt-level behavior contracts, not enforceable checks.

2. **Check artifact completion status**

   Run `openspec status --change "<name>" --json` to check artifact completion.

   Parse the JSON to understand:

   - `schemaName`: The workflow being used

   - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context

   - `artifacts`: List of artifacts with their status (`done`, `skipped`, or other)

   **If any artifacts are neither `done` nor `skipped`** (skipped artifacts satisfy the requirement - the change declares skip_specs):

   - Display warning listing incomplete artifacts

   - Ask the user to confirm they want to proceed

   - Proceed if user confirms

3. **Check task completion status**

   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.

   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).

   **If incomplete tasks found:**

   - Display warning showing count of incomplete tasks

   - Ask the user to confirm they want to proceed

   - Proceed if user confirms

   **If no tasks file exists:** Proceed without task-related warning.

4. **Assess delta spec sync state**

   Use `artifactPaths.specs.existingOutputPaths` from status JSON as the only

   delta-spec source. If the `specs` entry is missing or

   `existingOutputPaths` is empty, proceed without a sync prompt and do not infer

   delta specs from other artifacts.

   **If delta specs exist:**

   - Compare each delta spec with its corresponding main spec at `<planningHome.root>/openspec/specs/<capability-path>/spec.md` (use the store-aware `planningHome.root` from step 2, not a hardcoded repo path)

   - Determine what changes would be applied (adds, modifications, removals, renames)

   - Show a combined summary before prompting

   **Prompt options:**

   - If changes needed: "Sync now (recommended)", "Archive without syncing"

   - If already synced: "Archive now", "Sync anyway", "Cancel"

   Route on the answer:

   - "Cancel" — stop, do not archive

   - "Archive without syncing" or "Archive now" — proceed to archive

   - "Sync now" or "Sync anyway" — sync, then verify (below)

   - Anything else — ask again rather than archiving

   Before a selected sync writes any main spec, run

   `openspec instructions specs --change "<name>" --json` once with the same

   selected-root flags. Require a zero exit status and valid artifact-instruction

   JSON. If the lookup fails or returns invalid JSON, report the error and stop

   before writing any main spec or moving the change. A valid response with omitted

   `rules` is the no-rules case. Apply returned `rules` only to the content and

   form of main specs produced by this merge; do not use them as archive guidance,

   change CLI behavior, or copy the rule text into any output file.

   Then run the `openspec-sync-specs` workflow inline (agent-driven intelligent merge) for change '<name>', passing the delta spec analysis and the fetched specs-rule snapshot from above, and wait for it to finish. The inline sync must reuse that snapshot without fetching `specs` instructions again. Do not delegate it to a background task — step 5 would move `changeRoot` out from under a sync that is still reading it, leaving the change archived and the main specs never updated. If your agent can only run it by delegation, delegate synchronously and wait for the result.

   Then re-run the comparison from the top of this step against every capability that has a delta spec in `artifactPaths.specs.existingOutputPaths` — not only the ones the sync reports it touched. A successful sync leaves nothing left to apply, so each capability must now read as already synced:

   - ADDED requirements present

   - MODIFIED requirements carrying the scenario and description changes named in the delta, with their other scenarios intact

   - REMOVED requirements gone — and where this sync retired a capability (removed its last requirement, leaving `## Requirements` empty), its main spec deleted rather than left empty; a spec the sync deliberately kept and reported is also a match

   - RENAMED requirements present under the new name and absent under the old one

   If the sync failed, or any capability does not match, report what differs and stop — do not archive. Nothing has moved and `changeRoot` is intact, so the user can fix the mismatch or re-run the sync and start the archive again.

5. **Perform the archive**

   Create an `archive` directory under `planningHome.changesDir` if it doesn't exist:

   ```bash

   mkdir -p "<planningHome.changesDir>/archive"

   ```

   Generate the target name: use the change name as-is when it already starts with a `YYYY-MM-DD-` prefix; otherwise prepend the current date as `YYYY-MM-DD-<change-name>`. Never stack a second date (same rule as `openspec archive`).

   **Check if target already exists:**

   - If yes: Fail with error, suggest renaming existing archive or using different date

   - If no: Move `changeRoot` to the archive directory

   ```bash

   mv "<changeRoot>" "<planningHome.changesDir>/archive/<target-name>"

   ```

6. **Display summary**

   Show archive completion summary including:

   - Change name

   - Schema that was used

   - Archive location

   - Whether specs were synced (if applicable)

   - Note about any warnings (incomplete artifacts/tasks)

**Output On Success**

```markdown

## Archive Complete

**Change:** <change-name>

**Schema:** <schema-name>

**Archived to:** the archive path derived from `planningHome.changesDir`/<target-name>/

**Specs:** <"✓ Synced to main specs" only if the step 4 verification passed; otherwise "No delta specs" or "Sync skipped">

<"All artifacts complete. All tasks complete." — or, if archived with warnings, list them instead (e.g. "Archived with 2 incomplete tasks")>

```

**Guardrails**

- Announce the selected change; prompt for selection when it is ambiguous

- Use artifact graph (openspec status --json) for completion checking

- Don't block archive on warnings - just inform and confirm

- Preserve .openspec.yaml when moving to archive (it moves with the directory)

- Show clear summary of what happened

- If sync is requested, run the `openspec-sync-specs` workflow inline (agent-driven)

- Never archive while a spec sync is still in flight — run the sync inline and verify the main specs before moving `changeRoot`

- If delta specs exist, always run the sync assessment and show the combined summary before prompting

- Apply relevant runtime context and report conflicts; operation guidance remains advisory

- Consider every guidance entry and explain any inapplicable or conflicting advice

- Existing CLI checks, resolved paths, prompts, and command contracts are unchanged

- Artifact rules constrain only the specs being written and are never operation guidance

- Never copy runtime context, operation guidance, or artifact-rule text verbatim into output files