Skip to content

docs(openspec): align requirements with current behavior #1919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
clay-good merged 3 commits into from
Sep 29, 2026
Merged

docs(openspec): align requirements with current behavior #1919

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a020527
docs(openspec): correct 4 requirements that the code has outgrown
openspec-cloud[bot] Sep 18, 2026
9096d9c
docs(openspec): harden drift corrections
clay-good Sep 28, 2026
88979ee
docs(openspec): clarify header normalization
clay-good Sep 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions openspec/specs/cli-artifact-workflow/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,17 +183,6 @@ The system SHALL provide consistent output formatting.
- **WHEN** loading change state takes time
- **THEN** the system displays a spinner during loading

### Requirement: Experimental Isolation
The system SHALL implement artifact workflow commands in isolation for easy removal.

#### Scenario: Single file implementation
- **WHEN** artifact workflow feature is implemented
- **THEN** all commands are in `src/commands/artifact-workflow.ts`

#### Scenario: Help text marking
- **WHEN** user runs `--help` on any artifact workflow command
- **THEN** help text indicates the command is experimental

### Requirement: Schema Apply Block

The system SHALL support an `apply` block in schema definitions that controls when and how implementation begins.
Expand Down
6 changes: 3 additions & 3 deletions openspec/specs/cli-config/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,9 +182,9 @@ The `openspec config profile` command SHALL provide an action-first interactive

- **WHEN** user runs `openspec config profile` interactively
- **THEN** the first prompt SHALL offer:
- `Change delivery + workflows`
- `Change delivery only`
- `Change workflows only`
- `Delivery and workflows`
- `Delivery only`
- `Workflows only`
- `Keep current settings (exit)`

#### Scenario: Delivery prompt marks current selection
Expand Down
4 changes: 2 additions & 2 deletions openspec/specs/openspec-conventions/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,8 +99,8 @@ Requirement headers SHALL serve as unique identifiers for programmatic matching

- **WHEN** processing delta changes
- **THEN** use the `### Requirement: [Name]` header as the unique identifier
- **AND** match using normalized headers: `normalize(header) = trim(header)`
- **AND** compare headers with case-sensitive equality after normalization
- **AND** strip a closing run of `#` characters when a space or tab precedes it and only spaces or tabs follow it, then trim surrounding whitespace
- **AND** compare normalized requirement names with case-sensitive equality

#### Scenario: Handling requirement renames

Expand Down
Loading