You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
question: why achive skill or command relies on llm to manually merge specs why it does not use openspec archive cli command? #656
changed the title [-]question: why achieve skill or command relies on llm to manually merge specs why it does not use openspec archive cli command?[/-][+]question: why achive skill or command relies on llm to manually merge specs why it does not use openspec archive cli command?[/+]on Feb 3, 2026
Both paths exist by design. openspec archive performs a deterministic structural merge of delta blocks (src/core/archive.ts). The archive/sync skill is intentionally agent-driven so the LLM can do partial merges — e.g. add one scenario to an existing requirement without re-emitting the whole block — and reconcile prose, which the structural CLI merge can't (see the note in src/core/templates/workflows/sync-specs.ts:16). Closing as answered.
Activity
[-]question: why achieve skill or command relies on llm to manually merge specs why it does not use openspec archive cli command?[/-][+]question: why achive skill or command relies on llm to manually merge specs why it does not use openspec archive cli command?[/+]docs(proposal): add prevent-silent-spec-drop change
docs(proposal): add prevent-silent-spec-drop change
docs(proposal): add prevent-silent-spec-drop change
docs(proposal): add prevent-silent-spec-drop change
docs(proposal): add prevent-silent-spec-drop change
docs(proposal): add prevent-silent-spec-drop change
feat(workflows): route all archive surfaces through `openspec archive…
clay-good commentedon Aug 5, 2026
Both paths exist by design.
openspec archiveperforms a deterministic structural merge of delta blocks (src/core/archive.ts). The archive/sync skill is intentionally agent-driven so the LLM can do partial merges — e.g. add one scenario to an existing requirement without re-emitting the whole block — and reconcile prose, which the structural CLI merge can't (see the note insrc/core/templates/workflows/sync-specs.ts:16). Closing as answered.