fix: restore lean PR workflow with async main branch matrix

- PRs run only essential tests on ubuntu-latest (fast feedback)
- Main branch runs full cross-platform matrix asynchronously
- Separate required-checks for each workflow type
- Different timeouts: 10min for PR, 15min for matrix

CHANGELOG.md

@@ -1,29 +1,5 @@
 # @fission-ai/openspec
 
-## 0.5.0
-
-### Minor Changes
-
-- feat: implement Phase 1 E2E testing with cross-platform CI matrix
-
-  - Add shared runCLI helper in test/helpers/run-cli.ts for spawn testing
-  - Create test/cli-e2e/basic.test.ts covering help, version, validate flows
-  - Migrate existing CLI exec tests to use runCLI helper
-  - Extend CI matrix to bash (Linux/macOS) and pwsh (Windows)
-  - Split PR and main workflows for optimized feedback
-
-### Patch Changes
-
-- Make apply instructions more specific
-
-  Improve agent templates and slash command templates with more specific and actionable apply instructions.
-
-- docs: improve documentation and cleanup
-
-  - Document non-interactive flag for archive command
-  - Replace discord badge in README
-  - Archive completed changes for better organization
-
 ## 0.4.0
 
 ### Minor Changes

openspec/AGENTS.md

@@ -47,14 +47,12 @@ Skip proposal for:
 4. Run `openspec validate <id> --strict` and resolve any issues before sharing the proposal.
 
 ### Stage 2: Implementing Changes
-Track these steps as TODOs and complete them one by one.
 1. **Read proposal.md** - Understand what's being built
 2. **Read design.md** (if exists) - Review technical decisions
 3. **Read tasks.md** - Get implementation checklist
 4. **Implement tasks sequentially** - Complete in order
-5. **Confirm completion** - Ensure every item in `tasks.md` is finished before updating statuses
-6. **Update checklist** - After all work is done, set every task to `- [x]` so the list reflects reality
-7. **Approval gate** - Do not start implementation until the proposal is reviewed and approved
+5. **Mark complete immediately** - Update `- [x]` after each task
+6. **Approval gate** - Do not start implementation until the proposal is reviewed and approved
 
 ### Stage 3: Archiving Changes
 After deployment, create separate PR to:

openspec/changes/add-interactive-proposal-qa/proposal.md

@@ -1,13 +0,0 @@
-## Why
-A recent feature request highlighted that users struggle to scope proposals when all clarifications have to be typed manually. They want a guided interview that surfaces missing assumptions, recommends best-practice defaults, and produces a sharper brief before handing off to `/openspec/proposal`. Delivering an interactive Q&A flow keeps OpenSpec competitive with other planning assistants and shortens the loop between idea and actionable change specification.
-
-## What Changes
-- Add a dedicated `/openspec/proposal-qa` slash command that runs a structured discovery interview before drafting a change proposal.
-- Teach the agent to analyse the initial request, label what is already explicit versus ambiguous, and derive a small set of high-impact clarifying questions.
-- Require every question to include rationale, 2–4 recommended options with a default, and clear guidance on when to pick each option.
-- Capture the conversation outcome in a structured summary (problem, clarified decisions, open risks) that the user can accept or tweak before invoking `/openspec/proposal`.
-- Update onboarding (`init`/`update`) and slash command templates so the new command ships everywhere OpenSpec currently provisions proposal/apply/archive helpers.
-
-## Impact
-- Affected specs: assistant-proposal-qa (new), cli-init, cli-update, slash-commands-template (if modelled separately)
-- Affected code: `src/core/templates/slash-command-templates.ts`, `src/core/configurators/slash/*`, command scaffolding that writes `.claude/.cursor/.opencode` files, and associated tests.

openspec/changes/add-interactive-proposal-qa/specs/assistant-proposal-qa/spec.md

@@ -1,63 +0,0 @@
-# assistant-proposal-qa Specification
-
-## ADDED Requirements
-### Requirement: Interactive Proposal Q&A Command
-
-The system SHALL provide a `/openspec/proposal-qa` slash command that prepares users for `/openspec/proposal` by running a structured discovery interview.
-
-#### Scenario: Launching the proposal interview
-- **WHEN** the user runs `/openspec/proposal-qa Build a notifications digest`
-- **THEN** acknowledge the request and restate the draft problem statement
-- **AND** highlight what parts of the request are already concrete versus ambiguous (e.g., "Strong signals" and "Needs clarity")
-- **AND** outline the upcoming steps: targeted questions followed by a summary hand-off.
-
-#### Scenario: Honour non-interactive environments
-- **GIVEN** slash commands are invoked in a non-interactive environment (e.g., automation requesting defaults)
-- **WHEN** `/openspec/proposal-qa` is triggered with `--no-interactive`
-- **THEN** skip the question loop
-- **AND** produce a summary that records the request, recommended defaults, and instructions for editing manually before running `/openspec/proposal`.
-
-### Requirement: Targeted Clarifying Questions
-
-The interview SHALL adaptively surface 3–6 high-leverage questions that eliminate ambiguity in the proposal brief.
-
-#### Scenario: Ask one question at a time with rationale
-- **WHEN** the interview begins gathering answers
-- **THEN** select the next most risky/vague aspect of the feature
-- **AND** present a single question that includes:
-  - A short rationale explaining why the question matters for the proposal
-  - 2–4 recommended options formatted as a bulleted list with `**Default**` clearly marked
-  - Guidance for when to choose each option (one sentence per option)
-- **AND** wait for the user response (or `default`/`skip`) before showing another question.
-
-#### Scenario: Provide fallbacks when users defer
-- **WHEN** the user replies with `idk`, `default`, or leaves the answer empty
-- **THEN** accept the default option for that question
-- **AND** note in the transcript that the default was applied.
-
-#### Scenario: Capture bespoke answers
-- **WHEN** the user supplies an answer that does not match any recommended option
-- **THEN** accept the custom answer
-- **AND** record a short interpretation describing how it will shape the proposal.
-
-### Requirement: Synthesis and Handoff
-
-The interview SHALL produce an actionable summary that readies the agent to draft the formal change proposal.
-
-#### Scenario: Summarise discoveries before exit
-- **WHEN** the question loop completes (or is skipped)
-- **THEN** output a structured summary containing:
-  - Problem statement and scope recap
-  - Table or bullet list of decisions (question → final answer → reasoning/default flag)
-  - Noted risks, open questions, and assumptions to confirm in the proposal
-- **AND** recommend next actions: either ask for revisions, run `/openspec/proposal` with this summary, or request further research.
-
-#### Scenario: Provide reusable prompt snippet
-- **WHEN** the summary is generated
-- **THEN** include a copyable prompt block that the user can paste into `/openspec/proposal`
-- **AND** ensure the prompt references the summary decisions and flags any open items for follow-up.
-
-#### Scenario: Allow re-entry for more questions
-- **WHEN** the user indicates they want to refine further (e.g., "ask more" or "another pass")
-- **THEN** identify remaining ambiguous areas not yet questioned
-- **AND** continue with additional questions (up to the 6-question cap) before regenerating the summary.

openspec/changes/add-interactive-proposal-qa/specs/cli-init/spec.md

@@ -1,21 +0,0 @@
-## MODIFIED Requirements
-### Requirement: Slash Command Configuration
-The init command SHALL generate slash command files for supported editors using shared templates, including the interactive proposal interview instructions.
-
-#### Scenario: Generating slash commands for Claude Code
-- **WHEN** the user selects Claude Code during initialization
-- **THEN** create `.claude/commands/openspec/proposal.md`, `.claude/commands/openspec/proposal-qa.md`, `.claude/commands/openspec/apply.md`, and `.claude/commands/openspec/archive.md`
-- **AND** populate each file from shared templates so command text matches other tools
-- **AND** include guidance that the `proposal-qa` command runs the interactive discovery interview before `/openspec/proposal`.
-
-#### Scenario: Generating slash commands for Cursor
-- **WHEN** the user selects Cursor during initialization
-- **THEN** create `.cursor/commands/openspec-proposal.md`, `.cursor/commands/openspec-proposal-qa.md`, `.cursor/commands/openspec-apply.md`, and `.cursor/commands/openspec-archive.md`
-- **AND** populate each file from shared templates so command text matches other tools
-- **AND** include guidance that the `proposal-qa` command runs the interactive discovery interview before `/openspec/proposal`.
-
-#### Scenario: Generating slash commands for OpenCode
-- **WHEN** the user selects OpenCode during initialization
-- **THEN** create `.opencode/commands/openspec-proposal.md`, `.opencode/commands/openspec-proposal-qa.md`, `.opencode/commands/openspec-apply.md`, and `.opencode/commands/openspec-archive.md`
-- **AND** populate each file from shared templates so command text matches other tools
-- **AND** include guidance that the `proposal-qa` command runs the interactive discovery interview before `/openspec/proposal`.

openspec/changes/add-interactive-proposal-qa/specs/cli-update/spec.md

@@ -1,18 +0,0 @@
-## MODIFIED Requirements
-### Requirement: Slash Command Updates
-The update command SHALL refresh existing slash command files for configured tools, including the interactive proposal interview template, without creating new ones.
-
-#### Scenario: Updating slash commands for Claude Code
-- **WHEN** `.claude/commands/openspec/` contains `proposal.md`, `proposal-qa.md`, `apply.md`, and `archive.md`
-- **THEN** refresh each file using shared templates
-- **AND** ensure the `proposal-qa` template contains the interactive discovery instructions aligned with the latest assistant guidance.
-
-#### Scenario: Updating slash commands for Cursor
-- **WHEN** `.cursor/commands/` contains `openspec-proposal.md`, `openspec-proposal-qa.md`, `openspec-apply.md`, and `openspec-archive.md`
-- **THEN** refresh each file using shared templates
-- **AND** ensure the `proposal-qa` template contains the interactive discovery instructions aligned with the latest assistant guidance.
-
-#### Scenario: Updating slash commands for OpenCode
-- **WHEN** `.opencode/commands/` contains `openspec-proposal.md`, `openspec-proposal-qa.md`, `openspec-apply.md`, and `openspec-archive.md`
-- **THEN** refresh each file using shared templates
-- **AND** ensure the `proposal-qa` template contains the interactive discovery instructions aligned with the latest assistant guidance.

openspec/changes/add-interactive-proposal-qa/tasks.md

@@ -1,19 +0,0 @@
-## 1. Discovery & Design
-- [ ] 1.1 Audit existing slash command files (`src/core/templates/slash-command-templates.ts`, configurators, tests) to mirror tone/format.
-- [ ] 1.2 Draft conversational flow map covering request analysis, question generation heuristics, question formatting, and post-qa summary/next-steps.
-- [ ] 1.3 Validate the flow against the example repo in issue #85 to ensure parity with proven UX patterns (e.g., defaults, recommended answers).
-
-## 2. Specification Updates
-- [ ] 2.1 Add `assistant-proposal-qa` capability spec capturing requirements for analysis, questioning, summary, and hand-off UX.
-- [ ] 2.2 Update `cli-init` and `cli-update` specs so generated slash command files include the new `proposal-qa` command for all supported assistants.
-
-## 3. Implementation
-- [ ] 3.1 Extend `SlashCommandId` union, templates, and file writers to emit `/openspec/proposal-qa` with the new instructions body.
-- [ ] 3.2 Implement helper(s) that build recommended answer options from agent analysis (list of option label, description, default marker).
-- [ ] 3.3 Ensure question loop enforces 3–6 prompts, each with rationale and recommended default, and gracefully handles user-supplied alternatives.
-- [ ] 3.4 Update onboarding/update flows to write `.claude/.cursor/.opencode` command markdown for `proposal-qa` alongside existing commands.
-
-## 4. Validation & QA
-- [ ] 4.1 Add unit tests covering slash template rendering for the new command and regression tests for init/update scaffolding.
-- [ ] 4.2 Update documentation and examples (README, CHANGELOG as needed) showcasing how to use `/openspec/proposal-qa` and the resulting summary output.
-- [ ] 4.3 Run `openspec validate add-interactive-proposal-qa --strict` and full test suite (`pnpm test`) to confirm specs and tooling stay green.

openspec/changes/archive/2025-09-29-improve-init-onboarding/tasks.md

@@ -1,12 +0,0 @@
-## 1. Planning & Spec Updates
-- [x] 1.1 Confirm overlap with `add-multi-agent-init` and coordinate extend-mode flow
-- [x] 1.2 Update `openspec/specs/cli-init/spec.md` to capture multi-select onboarding requirements
-
-## 2. Implementation
-- [x] 2.1 Add multi-select support to the `openspec init` prompt, including indicators for existing tool configs
-- [x] 2.2 Enhance success messaging to summarize created/refreshed assets per tool
-- [x] 2.3 Ensure shared instruction template is applied consistently (CLAUDE.md, AGENTS.md, slash commands)
-
-## 3. Quality
-- [x] 3.1 Expand unit tests for init/update flows covering multi-select and summaries
-- [x] 3.2 Perform `openspec init` smoke test in a temp directory (document output)

openspec/changes/improve-cli-e2e-plan/tasks.md

@@ -4,6 +4,10 @@
 - [x] 1.3 Migrate the highest-value existing CLI exec tests (e.g., validate) onto `runCLI` and summarize Phase 1 coverage in this proposal for the next phase.
 
 ## 2. Phase 2 – Expand Cross-Shell Validation
-- [x] 2.1 Exercise both entry points (`node dist/cli/index.js`, `bin/openspec.js`) in the spawn suite and add diagnostics for shell/OS context.
+- [ ] 2.1 Exercise both entry points (`node dist/cli/index.js`, `bin/openspec.js`) in the spawn suite and add diagnostics for shell/OS context.
 - [x] 2.2 Extend GitHub Actions to run the spawn suite on bash jobs for Linux/macOS and a `pwsh` job on Windows; capture shell/OS diagnostics and note follow-ups for additional shells.
 
+## 3. Phase 3 – Package Validation (Optional)
+- [ ] 3.1 Add a simple CI job on runners with registry access that runs `pnpm pack`, installs the tarball into a temp workspace (e.g., `pnpm add --no-save`), and executes `pnpm exec openspec --version`.
+- [ ] 3.2 If network-restricted environments can’t exercise installs, skip the job and note the limitation in this proposal’s rollout log.
+- [ ] 3.3 Close out the enumerated hardening items: extend `.gitattributes` to cover packaged assets, enforce executable bits for CLI shims during CI, and finish the outstanding SIGINT handling work; update this proposal once they land.

openspec/changes/improve-deterministic-tests/tasks.md

@@ -21,5 +21,5 @@
 
 ## 5. Optional (Not Needed Now)
 - [x] 5.1 Add optional root param to discovery helpers (default process.cwd())
-
+- [ ] 5.2 Consider threading root through command constructors if ever required
 

openspec/changes/improve-init-onboarding/tasks.md

@@ -0,0 +1,12 @@
+## 1. Planning & Spec Updates
+- [ ] 1.1 Confirm overlap with `add-multi-agent-init` and coordinate extend-mode flow
+- [ ] 1.2 Update `openspec/specs/cli-init/spec.md` to capture multi-select onboarding requirements
+
+## 2. Implementation
+- [ ] 2.1 Add multi-select support to the `openspec init` prompt, including indicators for existing tool configs
+- [ ] 2.2 Enhance success messaging to summarize created/refreshed assets per tool
+- [ ] 2.3 Ensure shared instruction template is applied consistently (CLAUDE.md, AGENTS.md, slash commands)
+
+## 3. Quality
+- [ ] 3.1 Expand unit tests for init/update flows covering multi-select and summaries
+- [ ] 3.2 Perform `openspec init` smoke test in a temp directory (document output)

openspec/changes/remove-diff-command/tasks.md

@@ -26,6 +26,10 @@
   - Archive documentation
   - Change proposals
 
+## 6. Add Deprecation Notice (Optional Phase)
+- [ ] Consider adding a deprecation warning before full removal
+- [ ] Provide helpful message directing users to `openspec show` command
+
 ## 7. Testing
 - [x] Ensure all tests pass after removal
 - [x] Verify CLI help text no longer shows diff command

openspec/changes/update-agent-file-name/specs/cli-init/spec.md

@@ -25,16 +25,12 @@ The command SHALL generate required template files with appropriate content for
 
 ### Requirement: AI Tool Configuration Details
 
-The command SHALL properly configure selected AI tools with OpenSpec-specific instructions using a marker system.
-
 #### Scenario: Creating new CLAUDE.md
 - **WHEN** CLAUDE.md does not exist
 - **THEN** create new file with OpenSpec content wrapped in markers including reference to `@openspec/AGENTS.md`
 
 ### Requirement: Success Output
 
-The command SHALL provide clear, actionable next steps upon successful initialization.
-
 #### Scenario: Displaying success message
 - **WHEN** initialization completes successfully
 - **THEN** include prompt: "Please explain the OpenSpec workflow from openspec/AGENTS.md and how I should work with you on this project"

openspec/specs/cli-init/spec.md

@@ -3,7 +3,9 @@
 ## Purpose
 
 The `openspec init` command SHALL create a complete OpenSpec directory structure in any project, enabling immediate adoption of OpenSpec conventions with support for multiple AI coding assistants.
+
 ## Requirements
+
 ### Requirement: Progress Indicators
 
 The command SHALL display progress indicators during initialization to provide clear feedback about each step.
@@ -19,9 +21,11 @@ The command SHALL display progress indicators during initialization to provide c
   - Then success: "✔ AI tools configured"
 
 ### Requirement: Directory Creation
+
 The command SHALL create the complete OpenSpec directory structure with all required directories and files.
 
 #### Scenario: Creating OpenSpec structure
+
 - **WHEN** `openspec init` is executed
 - **THEN** create the following directory structure:
 ```
@@ -34,9 +38,11 @@ openspec/
 ```
 
 ### Requirement: File Generation
+
 The command SHALL generate required template files with appropriate content for immediate use.
 
 #### Scenario: Generating template files
+
 - **WHEN** initializing OpenSpec
 - **THEN** generate `AGENTS.md` containing complete OpenSpec instructions for AI assistants
 - **AND** generate `project.md` with project context template
@@ -48,14 +54,10 @@ The command SHALL configure AI coding assistants with OpenSpec instructions base
 #### Scenario: Prompting for AI tool selection
 
 - **WHEN** run interactively
-- **THEN** prompt the user with "Which AI tools do you use?" using a multi-select menu
-- **AND** list every available tool with a checkbox:
-  - Claude Code (creates or refreshes CLAUDE.md and slash commands)
-  - Cursor (creates or refreshes `.cursor/commands/*` slash commands)
-  - AGENTS.md standard (creates or refreshes AGENTS.md with OpenSpec markers)
-- **AND** show "(already configured)" beside tools whose managed files exist so users understand selections will refresh content
-- **AND** treat disabled tools as "coming soon" and keep them unselectable
-- **AND** allow confirming with Enter after selecting one or more tools
+- **THEN** prompt user to select AI tools to configure:
+  - Claude Code (updates/creates CLAUDE.md with OpenSpec markers)
+  - Cursor (future)
+  - Aider (future)
 
 ### Requirement: AI Tool Configuration Details
 
@@ -72,36 +74,105 @@ The command SHALL properly configure selected AI tools with OpenSpec-specific in
 - **THEN** create new file with OpenSpec content wrapped in markers:
 ```markdown
 <!-- OPENSPEC:START -->
-# OpenSpec Instructions
+# OpenSpec Project
 
-Instructions for AI coding assistants using OpenSpec for spec-driven development.
+This document provides instructions for AI coding assistants on how to use OpenSpec conventions for spec-driven development. Follow these rules precisely when working on OpenSpec-enabled projects.
+
+This project uses OpenSpec for spec-driven development. Specifications are the source of truth.
+
+See @openspec/AGENTS.md for detailed conventions and guidelines.
+<!-- OPENSPEC:END -->
+```
+
+#### Scenario: Updating existing CLAUDE.md
+
+- **WHEN** CLAUDE.md already exists
+- **THEN** preserve all existing content
+- **AND** insert OpenSpec content at the beginning of the file using markers
+- **AND** ensure markers don't duplicate if they already exist
+
+#### Scenario: Managing content with markers
+
+- **WHEN** using the marker system
+- **THEN** use `<!-- OPENSPEC:START -->` to mark the beginning of managed content
+- **AND** use `<!-- OPENSPEC:END -->` to mark the end of managed content
+- **AND** allow OpenSpec to update its content without affecting user customizations
+- **AND** preserve all content outside the markers intact
+
+WHY use markers:
+- Users may have existing CLAUDE.md instructions they want to keep
+- OpenSpec can update its instructions in future versions
+- Clear boundary between OpenSpec-managed and user-managed content
 
 ### Requirement: Interactive Mode
+
 The command SHALL provide an interactive menu for AI tool selection with clear navigation instructions.
 
 #### Scenario: Displaying interactive menu
-- **WHEN** run in fresh or extend mode
-- **THEN** present a looping select menu that lets users toggle tools with Enter and finish via a "Done" option
-- **AND** label already configured tools with "(already configured)" while keeping disabled options marked "coming soon"
-- **AND** change the prompt copy in extend mode to "Which AI tools would you like to add or refresh?"
-- **AND** display inline instructions clarifying that Enter toggles a tool and selecting "Done" confirms the list
+
+- **WHEN** run
+- **THEN** prompt user with: "Which AI tool do you use?"
+- **AND** show single-select menu with available tools:
+  - Claude Code
+- **AND** show disabled options as "coming soon" (not selectable):
+  - Cursor (coming soon)
+  - Aider (coming soon)  
+  - Continue (coming soon)
+
+#### Scenario: Navigating the menu
+
+- **WHEN** user is in the menu
+- **THEN** allow arrow keys to move between options
+- **AND** allow Enter key to select the highlighted option
 
 ### Requirement: Safety Checks
+
 The command SHALL perform safety checks to prevent overwriting existing structures and ensure proper permissions.
 
 #### Scenario: Detecting existing initialization
-- **WHEN** the `openspec/` directory already exists
-- **THEN** inform the user that OpenSpec is already initialized, skip recreating the base structure, and enter an extend mode
-- **AND** continue to the AI tool selection step so additional tools can be configured
-- **AND** display the existing-initialization error message only when the user declines to add any AI tools
+
+- **WHEN** `openspec/` directory already exists
+- **THEN** display error with ora fail indicator:
+  - "✖ Error: OpenSpec seems to already be initialized. Use 'openspec update' to update the structure."
+
+#### Scenario: Checking write permissions
+
+- **WHEN** checking initialization feasibility
+- **THEN** verify write permissions in the target directory silently
+- **AND** only display error if permissions are insufficient
 
 ### Requirement: Success Output
 
 The command SHALL provide clear, actionable next steps upon successful initialization.
 
 #### Scenario: Displaying success message
+
 - **WHEN** initialization completes successfully
-- **THEN** include prompt: "Please explain the OpenSpec workflow from openspec/AGENTS.md and how I should work with you on this project"
+- **THEN** display actionable prompts for AI-driven workflow:
+```
+✔ OpenSpec initialized successfully!
+
+Next steps - Copy these prompts to Claude:
+
+────────────────────────────────────────────────────────────
+1. Populate your project context:
+   "Please read openspec/project.md and help me fill it out
+    with details about my project, tech stack, and conventions"
+
+2. Create your first change proposal:
+   "I want to add [YOUR FEATURE HERE]. Please create an
+    OpenSpec change proposal for this feature"
+
+3. Learn the OpenSpec workflow:
+   "Please explain the OpenSpec workflow from openspec/AGENTS.md
+    and how I should work with you on this project"
+────────────────────────────────────────────────────────────
+```
+
+The prompts SHALL:
+- Be copy-pasteable for immediate use with AI tools
+- Guide users through the AI-driven workflow
+- Replace placeholder text ([YOUR FEATURE HERE]) with actual features
 
 ### Requirement: Exit Codes
 
@@ -116,52 +187,6 @@ The command SHALL use consistent exit codes to indicate different failure modes.
   - 2: Insufficient permissions (reserved for future use)
   - 3: User cancelled operation (reserved for future use)
 
-### Requirement: Additional AI Tool Initialization
-`openspec init` SHALL allow users to add configuration files for new AI coding assistants after the initial setup.
-
-#### Scenario: Configuring an extra tool after initial setup
-- **GIVEN** an `openspec/` directory already exists and at least one AI tool file is present
-- **WHEN** the user runs `openspec init` and selects a different supported AI tool
-- **THEN** generate that tool's configuration files with OpenSpec markers the same way as during first-time initialization
-- **AND** leave existing tool configuration files unchanged except for managed sections that need refreshing
-- **AND** exit with code 0 and display a success summary highlighting the newly added tool files
-
-### Requirement: Success Output Enhancements
-`openspec init` SHALL summarize tool actions when initialization or extend mode completes.
-
-#### Scenario: Showing tool summary
-- **WHEN** the command completes successfully
-- **THEN** display a categorized summary of tools that were created, refreshed, or skipped (including already-configured skips)
-- **AND** personalize the "Next steps" header using the names of the selected tools, defaulting to a generic label when none remain
-
-### Requirement: Exit Code Adjustments
-`openspec init` SHALL treat extend mode with no selected tools as a guarded error.
-
-#### Scenario: Preventing empty extend runs
-- **WHEN** OpenSpec is already initialized and the user selects no additional tools
-- **THEN** exit with code 1 after showing the existing-initialization guidance message
-
-### Requirement: Slash Command Configuration
-The init command SHALL generate slash command files for supported editors using shared templates.
-
-#### Scenario: Generating slash commands for Claude Code
-- **WHEN** the user selects Claude Code during initialization
-- **THEN** create `.claude/commands/openspec/proposal.md`, `.claude/commands/openspec/apply.md`, and `.claude/commands/openspec/archive.md`
-- **AND** populate each file from shared templates so command text matches other tools
-- **AND** each template includes instructions for the relevant OpenSpec workflow stage
-
-#### Scenario: Generating slash commands for Cursor
-- **WHEN** the user selects Cursor during initialization
-- **THEN** create `.cursor/commands/openspec-proposal.md`, `.cursor/commands/openspec-apply.md`, and `.cursor/commands/openspec-archive.md`
-- **AND** populate each file from shared templates so command text matches other tools
-- **AND** each template includes instructions for the relevant OpenSpec workflow stage
-
-#### Scenario: Generating slash commands for OpenCode
-- **WHEN** the user selects OpenCode during initialization
-- **THEN** create `.opencode/commands/openspec-proposal.md`, `.opencode/commands/openspec-apply.md`, and `.opencode/commands/openspec-archive.md`
-- **AND** populate each file from shared templates so command text matches other tools
-- **AND** each template includes instructions for the relevant OpenSpec workflow stage
-
 ## Why
 
 Manual creation of OpenSpec structure is error-prone and creates adoption friction. A standardized init command ensures:

openspec/specs/cli-update/spec.md

@@ -5,11 +5,22 @@
 As a developer using OpenSpec, I want to update the OpenSpec instructions in my project when new versions are released, so that I can benefit from improvements to AI agent instructions.
 ## Requirements
 ### Requirement: Update Behavior
+
 The update command SHALL update OpenSpec instruction files to the latest templates in a team-friendly manner.
 
 #### Scenario: Running update command
+
 - **WHEN** a user runs `openspec update`
-- **THEN** replace `openspec/AGENTS.md` with the latest template
+- **THEN** the command SHALL:
+  - Check if the `openspec` directory exists
+  - Replace `openspec/AGENTS.md` with the latest template (complete replacement)
+  - Update **only existing** AI tool configuration files (e.g., CLAUDE.md)
+    - Check each registered AI tool configurator
+    - For each configurator, check if its file exists
+    - Update only files that already exist using their markers
+    - Preserve user content outside markers
+    - **Never create new AI tool configuration files**
+  - Display success message listing updated files
 
 ### Requirement: Prerequisites
 
@@ -23,53 +34,39 @@ The command SHALL require an existing OpenSpec structure before allowing updates
 - **AND** exit with code 1
 
 ### Requirement: File Handling
+
 The update command SHALL handle file updates in a predictable and safe manner.
 
-#### Scenario: Updating files
-- **WHEN** updating files
-- **THEN** completely replace `openspec/AGENTS.md` with the latest template
-
-### Requirement: Tool-Agnostic Updates
-The update command SHALL handle file updates in a predictable and safe manner while respecting team tool choices.
-
 #### Scenario: Updating files
 
 - **WHEN** updating files
 - **THEN** completely replace `openspec/AGENTS.md` with the latest template
-- **AND** create or update the root-level `AGENTS.md` using the OpenSpec markers
 - **AND** update only the OpenSpec-managed blocks in **existing** AI tool files using markers
 - **AND** use the default directory name `openspec`
 - **AND** be idempotent (repeated runs have no additional effect)
-- **AND** respect team members' AI tool choices by not creating additional tool files beyond the root `AGENTS.md`
+- **AND** respect team members' AI tool choices by not creating unwanted files
+
+### Requirement: Tool-Agnostic Updates
+
+The update command SHALL update only existing AI tool configuration files and SHALL NOT create new ones.
+
+#### Scenario: Updating existing tool files
+
+- **WHEN** a user runs `openspec update`
+- **THEN** update each AI tool configuration file that exists (e.g., CLAUDE.md, COPILOT.md)
+- **AND** do not create missing tool configuration files
+- **AND** preserve user content outside OpenSpec markers
 
 ### Requirement: Core Files Always Updated
+
 The update command SHALL always update the core OpenSpec files and display an ASCII-safe success message.
 
 #### Scenario: Successful update
+
 - **WHEN** the update completes successfully
 - **THEN** replace `openspec/AGENTS.md` with the latest template
-
-### Requirement: Slash Command Updates
-The update command SHALL refresh existing slash command files for configured tools without creating new ones.
-
-#### Scenario: Updating slash commands for Claude Code
-- **WHEN** `.claude/commands/openspec/` contains `proposal.md`, `apply.md`, and `archive.md`
-- **THEN** refresh each file using shared templates
-- **AND** ensure templates include instructions for the relevant workflow stage
-
-#### Scenario: Updating slash commands for Cursor
-- **WHEN** `.cursor/commands/` contains `openspec-proposal.md`, `openspec-apply.md`, and `openspec-archive.md`
-- **THEN** refresh each file using shared templates
-- **AND** ensure templates include instructions for the relevant workflow stage
-
-#### Scenario: Updating slash commands for OpenCode
-- **WHEN** `.opencode/commands/` contains `openspec-proposal.md`, `openspec-apply.md`, and `openspec-archive.md`
-- **THEN** refresh each file using shared templates
-- **AND** ensure templates include instructions for the relevant workflow stage
-
-#### Scenario: Missing slash command file
-- **WHEN** a tool lacks a slash command file
-- **THEN** do not create a new file during update
+- **AND** update existing AI tool configuration files within markers
+- **AND** display the message: "Updated OpenSpec instructions"
 
 ## Edge Cases
 

openspec/specs/cli-validate/spec.md

@@ -199,12 +199,3 @@ The validate command SHALL handle ambiguous names and explicit type overrides to
 - **THEN** the CLI SHALL not display interactive prompts
 - **AND** SHALL print non-interactive hints or chosen outputs as appropriate
 
-### Requirement: Parser SHALL handle cross-platform line endings
-The markdown parser SHALL correctly identify sections regardless of line ending format (LF, CRLF, CR).
-
-#### Scenario: Required sections parsed with CRLF line endings
-- **GIVEN** a change proposal markdown saved with CRLF line endings
-- **AND** the document contains `## Why` and `## What Changes`
-- **WHEN** running `openspec validate <change-id>`
-- **THEN** validation SHALL recognize the sections and NOT raise parsing errors
-

openspec/specs/cli-view/spec.md

@@ -36,14 +36,28 @@ The dashboard SHALL display a summary section with key project metrics.
 - **THEN** summary shows zero counts for all metrics
 
 ### Requirement: Active Changes Display
+
 The dashboard SHALL show active changes with visual progress indicators.
 
+#### Scenario: Active changes with progress bars
+
+- **WHEN** there are in-progress changes with tasks
+- **THEN** system displays each change with change name left-aligned
+- **AND** visual progress bar using Unicode characters
+- **AND** percentage completion on the right
+
 #### Scenario: Active changes ordered by completion percentage
+
 - **WHEN** multiple active changes are displayed with progress information
 - **THEN** list them sorted by completion percentage ascending so 0% items appear first
 - **AND** treat missing progress values as 0% for ordering
 - **AND** break ties by change identifier in ascending alphabetical order to keep output deterministic
 
+#### Scenario: No active changes
+
+- **WHEN** all changes are completed or no changes exist
+- **THEN** active changes section is omitted from display
+
 ### Requirement: Completed Changes Display
 
 The dashboard SHALL list completed changes in a separate section.

openspec/specs/openspec-conventions/spec.md

@@ -14,9 +14,11 @@ OpenSpec conventions SHALL mandate a structured spec format with clear requireme
 - **THEN** authors SHALL use `### Requirement: ...` followed by at least one `#### Scenario: ...` section
 
 ### Requirement: Project Structure
+
 An OpenSpec project SHALL maintain a consistent directory structure for specifications and changes.
 
 #### Scenario: Initializing project structure
+
 - **WHEN** an OpenSpec project is initialized
 - **THEN** it SHALL have this structure:
 ```

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fission-ai/openspec",
-  "version": "0.5.0",
+  "version": "0.4.0",
   "description": "AI-native system for spec-driven development",
   "keywords": [
     "openspec",

src/core/templates/agents-template.ts

@@ -47,14 +47,12 @@ Skip proposal for:
 4. Run \`openspec validate <id> --strict\` and resolve any issues before sharing the proposal.
 
 ### Stage 2: Implementing Changes
-Track these steps as TODOs and complete them one by one.
 1. **Read proposal.md** - Understand what's being built
 2. **Read design.md** (if exists) - Review technical decisions
 3. **Read tasks.md** - Get implementation checklist
 4. **Implement tasks sequentially** - Complete in order
-5. **Confirm completion** - Ensure every item in \`tasks.md\` is finished before updating statuses
-6. **Update checklist** - After all work is done, set every task to \`- [x]\` so the list reflects reality
-7. **Approval gate** - Do not start implementation until the proposal is reviewed and approved
+5. **Mark complete immediately** - Update \`- [x]\` after each task
+6. **Approval gate** - Do not start implementation until the proposal is reviewed and approved
 
 ### Stage 3: Archiving Changes
 After deployment, create separate PR to:

src/core/templates/slash-command-templates.ts

@@ -22,12 +22,10 @@ const proposalReferences = `**Reference**
 - Explore the codebase with \`rg <keyword>\`, \`ls\`, or direct file reads so proposals align with current implementation realities.`;
 
 const applySteps = `**Steps**
-Track these steps as TODOs and complete them one by one.
 1. Read \`changes/<id>/proposal.md\`, \`design.md\` (if present), and \`tasks.md\` to confirm scope and acceptance criteria.
 2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
-3. Confirm completion before updating statuses—make sure every item in \`tasks.md\` is finished.
-4. Update the checklist after all work is done so each task is marked \`- [x]\` and reflects reality.
-5. Reference \`openspec list\` or \`openspec show <item>\` when additional context is required.`;
+3. Mark each task \`- [x]\` immediately after completing it to keep the checklist in sync.
+4. Reference \`openspec list\` or \`openspec show <item>\` when additional context is required.`;
 
 const applyReferences = `**Reference**
 - Use \`openspec show <id> --json --deltas-only\` if you need additional context from the proposal while implementing.`;