From: Jérôme Benoit Date: Thu, 15 Jan 2026 18:17:28 +0000 (+0100) Subject: chore: update OpenSpec artefacts X-Git-Url: https://git.piment-noir.org/?a=commitdiff_plain;h=e182fe4bb66c1c60a294a3c55fd067772ab0e56a;p=e-mobility-charging-stations-simulator.git chore: update OpenSpec artefacts Signed-off-by: Jérôme Benoit --- diff --git a/.opencode/command/openspec-archive.md b/.opencode/command/openspec-archive.md index 8d60d358..5b564fb5 100644 --- a/.opencode/command/openspec-archive.md +++ b/.opencode/command/openspec-archive.md @@ -21,7 +21,7 @@ description: Archive a deployed OpenSpec change and update specs. 2. Validate the change ID by running `openspec list` (or `openspec show `) and stop if the change is missing, already archived, or otherwise not ready to archive. 3. Run `openspec archive --yes` so the CLI moves the change and applies spec updates without prompts (use `--skip-specs` only for tooling-only work). 4. Review the command output to confirm the target specs were updated and the change landed in `changes/archive/`. -5. Validate with `openspec validate --strict` and inspect with `openspec show ` if anything looks off. +5. Validate with `openspec validate --strict --no-interactive` and inspect with `openspec show ` if anything looks off. **Reference** diff --git a/.opencode/command/openspec-proposal.md b/.opencode/command/openspec-proposal.md index 9282a4fd..fcd086f8 100644 --- a/.opencode/command/openspec-proposal.md +++ b/.opencode/command/openspec-proposal.md @@ -26,7 +26,7 @@ $ARGUMENTS 4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs. 5. Draft spec deltas in `changes//specs//spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant. 6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work. -7. Validate with `openspec validate --strict` and resolve every issue before sharing the proposal. +7. Validate with `openspec validate --strict --no-interactive` and resolve every issue before sharing the proposal. **Reference** diff --git a/openspec/AGENTS.md b/openspec/AGENTS.md index 45ef8a6b..8de8eb8a 100644 --- a/openspec/AGENTS.md +++ b/openspec/AGENTS.md @@ -9,7 +9,7 @@ Instructions for AI coding assistants using OpenSpec for spec-driven development - Pick a unique `change-id`: kebab-case, verb-led (`add-`, `update-`, `remove-`, `refactor-`) - Scaffold: `proposal.md`, `tasks.md`, `design.md` (only if needed), and delta specs per affected capability - Write deltas: use `## ADDED|MODIFIED|REMOVED|RENAMED Requirements`; include at least one `#### Scenario:` per requirement -- Validate: `openspec validate [change-id] --strict` and fix issues +- Validate: `openspec validate [change-id] --strict --no-interactive` and fix issues - Request approval: Do not start implementation until proposal is approved ## Three-Stage Workflow @@ -50,7 +50,7 @@ Skip proposal for: 1. Review `openspec/project.md`, `openspec list`, and `openspec list --specs` to understand current context. 2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, optional `design.md`, and spec deltas under `openspec/changes//`. 3. Draft spec deltas using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement. -4. Run `openspec validate --strict` and resolve any issues before sharing the proposal. +4. Run `openspec validate --strict --no-interactive` and resolve any issues before sharing the proposal. ### Stage 2: Implementing Changes @@ -71,7 +71,7 @@ After deployment, create separate PR to: - Move `changes/[name]/` → `changes/archive/YYYY-MM-DD-[name]/` - Update `specs/` if capabilities changed - Use `openspec archive --skip-specs --yes` for tooling-only changes (always pass the change ID explicitly) -- Run `openspec validate --strict` to confirm the archived change passes checks +- Run `openspec validate --strict --no-interactive` to confirm the archived change passes checks ## Before Any Task @@ -121,7 +121,7 @@ openspec validate # Bulk validation mode # Debugging openspec show [change] --json --deltas-only -openspec validate [change] --strict +openspec validate [change] --strict --no-interactive ``` ### Command Flags @@ -354,7 +354,7 @@ Example for RENAMED: ```bash # Always use strict mode for comprehensive checks -openspec validate [change] --strict +openspec validate [change] --strict --no-interactive # Debug delta parsing openspec show [change] --json | jq '.deltas' @@ -391,7 +391,7 @@ Users MUST provide a second factor during login. EOF # 4) Validate -openspec validate $CHANGE --strict +openspec validate $CHANGE --strict --no-interactive ``` ## Multi-Capability Example @@ -515,7 +515,7 @@ Only add complexity with: ```bash openspec list # What's in progress? openspec show [item] # View details -openspec validate --strict # Is it correct? +openspec validate --strict --no-interactive # Is it correct? openspec archive [--yes|-y] # Mark complete (add --yes for automation) ```