Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

archive and sync skills merge every `specs/**/*.md` as a delta spec, including files `validate` rejects

Aperta Adatta ai principianti
  • Qualcosa non va?
#2,173 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@clay-good ci sta già lavorando.

Dal 29/10/2026.

  • #2174 di @clay-good — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
78/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
developer-experience, tooling

Direzione di ricerca

Read the archive-change.ts step 4 and sync-specs.ts step 3 instructions, then compare their use of artifactPaths.specs.existingOutputPaths with the <capability-path>/spec.md rule and discoverSpecFiles. Check the generated skill templates on main and run the archive and sync workflows with a stray specs/user-auth/notes.md file. Done when both workflows stop before writing main specs and explain how to move those requirements into spec.md; verify the valid spec.md path still syncs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug needs-triage
What you were trying to do

Archive a change with /opsx:archive, or sync it with /opsx:sync, when a delta was written to a second file beside a capability's spec.md, for example specs/user-auth/notes.md.

What happened

#1869 fixed the CLI side of this. instructions apply now warns ("specs/user-auth/notes.md is not a capability's spec.md, so openspec validate rejects it and archive never merges it"), and openspec archive validates and refuses the change.

The agent workflows still take their delta set from artifactPaths.specs.existingOutputPaths. That list resolves the schema glob specs/**/*.md, so it includes notes.md:

  • archive-change.ts step 4: "Use artifactPaths.specs.existingOutputPaths … as the only delta-spec source".
  • sync-specs.ts step 3: "Sync every path in existingOutputPaths".

Neither workflow runs openspec validate, and neither checks the <capability-path>/spec.md shape. The agent therefore merges notes.md's requirements into openspec/specs/user-auth/spec.md and moves the change to the archive, which is exactly what the CLI now refuses to do. The skills and the CLI disagree about which files are deltas.

Open PR #1796 delegates the final move to openspec archive --skip-specs. CLI validation would then refuse at the end, but only after the skill's inline sync has already written the stray requirements into the main specs. So that PR does not close this.

What you expected instead

The archive and sync skills treat only specs/<capability-path>/spec.md as delta specs, the same set discoverSpecFiles reads. For any other file under specs/, they stop before writing a main spec and tell the user to move its requirements into the capability's spec.md, as the apply warning says. Running openspec validate <name> before the sync would cover this and any future validate/skill drift.

Minimal steps to reproduce
openspec init --tools claude
openspec new change add-logout
# write proposal.md, design.md, tasks.md
mkdir -p openspec/changes/add-logout/specs/user-auth
# specs/user-auth/spec.md   -> "## ADDED Requirements / ### Requirement: Password Login" + scenario
# specs/user-auth/notes.md  -> "## ADDED Requirements / ### Requirement: Logout" + scenario
openspec status --change add-logout --json | jq '.artifactPaths.specs.existingOutputPaths'
# [".../specs/user-auth/notes.md", ".../specs/user-auth/spec.md"]
openspec validate add-logout   # exit 1

Then run /opsx:archive add-logout. Step 4 reads both paths as delta specs and offers "Sync now". The sync merges Logout into the main spec, and step 5 moves the change.

OpenSpec version

Reproduced on 1.14.3. The templates are unchanged on main @ 6d04a1b (1.15.0). Related: #1869 (CLI side, closed), #2163 (archive reads only artifactPaths.specs, open), #1796 (open PR).

Coding agent and model

Claude Code, Claude Opus. Found by reading the generated skills against status/validate output; the gap is in the instruction text.

Agent session trace

No response

OS and Node version

macOS, Node 24

Lingua principale
TypeScript
Stelle
73k
Fork
5k
Merge medio
2g 12h
PR unite (30g)
54

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Fission-AI/OpenSpec

Tutte le issue di Fission-AI/OpenSpec

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.