docs(openspec): update 3 requirements to match the code

[openspec-cloud]

Last scanned: 2026-10-09 23:10 UTC

▶ View full results and scan again

The assessment found 3 requirements that no longer matched the code. OpenSpec Cloud proposed updates only for those requirements.

The scan was incomplete: 15 requirements could not be verified. These updates cover only citation-gated findings; this pull request is not a clean result for the repository.

The scan reported 38 findings in total. The other 35 need a person rather than a specification edit and stay in the check.

Scope: this pull request edits openspec/ files only.

Review Files changed before merging. OpenSpec Cloud never approves or merges this proposal.

Scan history and manual trigger

• 2026-10-09 23:10 UTC · View results

Comment /openspec-cloud full on this correction pull request to request a fresh repository scan.

View the complete originating check.

🔎 3 requirements drifted — 3 at stale specs.

AI-generated · A citation proves the line exists, not that it makes the case — verify before acting.

Not a clean result. 15 requirement(s) were not verified.

🟣 Stale specs (1)

🟣 Confirmation Behavior — spec is out of date · high

Expected — openspec/specs/cli-archive/spec.md:206

The spec update confirmation SHALL provide clear visibility into changes before they are applied.

Observed — src/core/archive.ts:1770

default: true
First observed in retained OpenSpec Cloud history — 9111a76.

Next → update the requirement to match the code.

Proposed requirement update:

--- a/openspec/specs/cli-archive/spec.md
+++ b/openspec/specs/cli-archive/spec.md
@@ -224,12 +224,12 @@
   EXISTING specs to be updated:
     - cli-init (from changes/update-init-command/specs/cli-init/spec.md)
   
-  Update 2 specs and archive 'add-archive-command'? [y/N]:
-  ```
-#### Scenario: Handling confirmation response
-
-- **WHEN** waiting for user confirmation
-- **THEN** default to "No" for safety (require explicit "y" or "yes")
+  Update 2 specs and archive 'add-archive-command'? [Y/n]:
+  ```
+#### Scenario: Handling confirmation response
+
+- **WHEN** waiting for user confirmation
+- **THEN** default to "Yes" for safety (require explicit "n" or "no")
 - **AND** skip confirmation when `--yes` or `-y` flag is provided
 
 #### Scenario: User declines confirmation

2 findings are omitted from this field to stay within its limit; review the complete originating check for every finding.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: Fission-AI/OpenSpec/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8544755e-6c74-4c44-b2c3-2c75a16335c2

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[openspec-cloud]

▶ View full results and scan again

🔎 1 requirement drifted — 1 at stale spec.

AI-generated · A citation proves the line exists, not that it makes the case — verify before acting.

Checked the 3 requirements selected for this PR at a03f376 (255 total).
Only findings tied to this PR’s changed lines or requirements are shown here.

🟣 Resolve schema with updated precedence order — spec is out of date · high

Expected — openspec/specs/schema-resolution/spec.md:109

CLI flag, change metadata, project config, planning-home default, hardcoded default.

Observed — src/utils/change-metadata.ts:227

* 4. Default 'spec-driven'
First observed in retained OpenSpec Cloud history — a03f376 in PR #2065.

Next → update the requirement to match the code.

Agent prompt

In openspec/specs/schema-resolution/spec.md (line 109), update the requirement that is contradicted by src/utils/change-metadata.ts:227. Rewrite only that requirement and its scenarios to match the cited code. Edit only that spec file and do not change any code.

View results · Click Refresh, then Scan again in the check. Or comment /openspec-cloud.