What problem does it solve? Teams using OpenSpec across multiple repositories need a single, consistent answer to where change proposals, designs, tasks, and specs live — inside an adopted repository or in a project-local store — without each workflow skill re-deciding it or accidentally writing into unadopted repos. ## Core Features & Use Cases - Native tree layout reference: Documents the canonical openspec/changes/ and openspec/specs/ directory structure, where active work is derived from un-archived change directories with no pointer files. - Per-scope backend resolution: Implements an ask-once, persist, reuse flow that saves { mode, root } per repository in repos.json, with project-wide changes defaulting to the project store. - Skill-owned fold and archive: Describes the git-mv plus markdown fold archival procedure (ADDED appends, MODIFIED rewrites, REMOVED deletes) with all-or-nothing failure semantics and no external CLI. - Use Case: When running a grill or writing-plans workflow on a linked repository, the skill checks repos.json for a saved OpenSpec config, asks one adoption question if unconfigured, persists the answer, and only then writes artifacts to the resolved root. ## Quick Start Ask the AI to resolve and persist the OpenSpec storage backend for a linked repository before writing any change artifacts.
