This repository (Asymmetric-al/core)
These repo-owned sections sit above the official OpenSpec skill. Reconcile this
overlay after upstream refreshes before running bun run skills:sync.
Use the locally pinned CLI only: bun run openspec -- <command>. Do not invoke
@latest. Core does not use Stores. Pass an explicit change ID before any
mutating OpenSpec operation. Follow AGENTS.md and docs/ai/rules/openspec.md.
Do not bypass TDD, exact base-maia, data-access boundaries, security, or
repository checks. Do not archive unmerged or incomplete work. Do not run
openspec update against the live customized repository. Do not treat product
runtime Eve as a coding agent.
Allowed-tools metadata includes Bash(bun:*) so the local wrapper can run.
Triggers
- The matching OpenSpec workflow is requested: Explore, Propose, Update, Apply, Verify, Sync, or Archive.
- Numbered commands
/1-start-projectthrough/4-close-projectwrap these workflows.
Workflow
- Read
openspec/config.yaml,openspec/project.md, and the relevant specs or active change. - Invoke
bun run openspec --with the explicit change ID for mutating work. - Keep Core TDD, UI, data-boundary, and Guardian rules in force.
- Leave the change active until implementation has merged.
Checklist
- Local pinned CLI used via
bun run openspec -- - Explicit change ID used for mutating operations
- Stores were not introduced
- Incomplete or unmerged work was not archived
-
openspec updatewas not run against the live repo - Product Eve was not treated as a coding agent
Archive a completed change in the experimental workflow.
Project check: Before writing, run bun run openspec -- list --json and confirm the root is the Core checkout containing its local openspec/ tree. A missing root, Store declaration, or external root is a configuration error: stop before writing and report it. Do not initialize a root or select an external Store.
<capability-path> is the spec directory relative to specs/ (for example, user-auth or identity/user-auth). Preserve the full path from each delta spec when resolving its main spec.
Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
Steps
Select the change
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run
openspec list --jsonto get available changes and ask the user to select one
When prompting, show only active changes (not already archived). Include the schema used for each change if available.
Always announce: "Using change: " and how to override (e.g.,
/openspec-archive-change <other>).Load current archive inputs before the existing archive checks:
After resolving the selected change and planning root, run:
openspec instructions archive --change "<name>" --jsonKeep the same selected-root flags on this command. This lookup is advisory and optional: it only supplies extra prompt inputs, so it must never block archiving. If it exits non-zero or returns invalid JSON — for example on an older CLI that does not support this command yet — continue the archive workflow with no context and no operation guidance. Do not report an error and do not stop.
A successful response may omit both optional fields. Treat
contextas a required prompt-level input: read and consider it, and apply relevant project facts, conventions, and constraints. TreatoperationGuidanceas optional additive advice: read and consider every entry, and follow entries that are applicable and compatible with the built-in archive workflow.Keep both fields separate from built-in steps, explicit user choices, resolved paths, CLI checks, and command contracts. If context conflicts with one of those controlling inputs, report the conflict and preserve the controlling value. If guidance is inapplicable or conflicts with a controlling input, do not follow it and explain why. Do not infer replacement paths, skipped prompts, or flags from either field, and do not copy their text verbatim into specs, change artifacts, or archive summaries unless the user separately asks for it. These are prompt-level behavior contracts, not enforceable checks.
Check artifact completion status
Run
openspec status --change "<name>" --jsonto check artifact completion.Parse the JSON to understand:
schemaName: The workflow being usedplanningHome,changeRoot,artifactPaths, andactionContext: path and scope contextartifacts: List of artifacts with their status (done,skipped, or other)
If any artifacts are neither
donenorskipped(skipped artifacts satisfy the requirement - the change declares skip_specs):- Display warning listing incomplete artifacts
- Ask the user to confirm they want to proceed
- Proceed if user confirms
Check task completion status
Run
openspec list --jsonwith the same selected-root flags and find the entry inchangeswhosenameexactly matches the selected change. Require exactly one match and nonnegative integertotalTasksandcompletedTasks, withcompletedTasks <= totalTasks. The CLI resolves the schema's tracked task files, including custom artifact names, output paths, and globs. Incomplete tasks =totalTasks - completedTasks.Do not infer task completion from artifact status or the absence of a top-level
tasks.md. If the lookup fails, returns invalid JSON, omits or duplicates the selected change, or returns invalid counts, report the problem and stop before syncing or archiving. The CLI counts onlyx/Xcheckbox markers as complete; other markers, including unfamiliar ones, remain incomplete.If incomplete tasks found:
- Display warning showing count of incomplete tasks
- Ask the user to confirm they want to proceed
- Proceed if user confirms
If
totalTasksis zero: Proceed without a task-related warning.Assess delta spec sync state
Use
artifactPaths.specs.existingOutputPathsfrom status JSON as the only delta-spec source. If thespecsentry is missing orexistingOutputPathsis empty, proceed without a sync prompt and do not infer delta specs from other artifacts.If delta specs exist:
- Compare each delta spec with its corresponding main spec at
<planningHome.root>/openspec/specs/<capability-path>/spec.md(use the store-awareplanningHome.rootfrom step 2, not a hardcoded repo path) - A missing main spec is not automatically "already synced". For a new capability, the main spec is an output of the sync, not an input:
- If the delta has MODIFIED or RENAMED requirements, report that only ADDED requirements can create a new main spec and mark that capability as sync-blocked. Never invent a requirement that has no current version.
- Otherwise, if the delta has only REMOVED requirements and the change's
.openspec.yamldeclaresretire_capabilities: true, the capability is already retired: count it as already synced, warn that there is nothing left to remove, and do not recreate the main spec. Apply this rule both now and when verifying a completed sync. - Otherwise, if the delta has no ADDED requirements, report that no sync is possible and mark that capability as sync-blocked. For a REMOVED-only delta, warn that there is no main spec to remove from and leave the main-spec tree unchanged.
openspec archiverefuses the unmarked REMOVED-only case withSpec must have at least one requirement. - Otherwise, count the capability as needing sync and name it in the summary (
<capability-path>: new main spec will be created). If the delta also has REMOVED requirements, warn that they will be ignored because there is no main spec to remove from. The sync creates the main spec from only the delta's ADDED requirements, exactly asopenspec archivedoes.
- Determine what changes would be applied (adds, modifications, removals, renames)
- Continue assessing the remaining capabilities even when one is sync-blocked. Show a combined summary before prompting.
Prompt options:
- If any capability is sync-blocked: explain why and offer only "Archive without syncing", "Cancel"
- Otherwise, if changes needed: "Sync now (recommended)", "Archive without syncing"
- Otherwise, if already synced: "Archive now", "Sync anyway", "Cancel"
Route on the answer:
- "Cancel" — stop, do not archive
- "Archive without syncing" or "Archive now" — proceed to archive
- "Sync now" or "Sync anyway" — sync, then verify (below). Do not start any sync while a capability is sync-blocked; explain the blocker and repeat the available choices.
- Anything else — ask again rather than archiving
Before a selected sync writes any main spec, run
openspec instructions specs --change "<name>" --jsononce with the same selected-root flags. Require a zero exit status and valid artifact-instruction JSON. If the lookup fails or returns invalid JSON, report the error and stop before writing any main spec or moving the change. A valid response with omittedrulesis the no-rules case. Apply returnedrulesonly to the content and form of main specs produced by this merge; do not use them as archive guidance, change CLI behavior, or copy the rule text into any output file.Then run the
openspec-sync-specsworkflow inline (agent-driven intelligent merge) for change '', passing the delta spec analysis and the fetched specs-rule snapshot from above, and wait for it to finish. The inline sync must reuse that snapshot without fetchingspecsinstructions again. Do not delegate it to a background task — step 5 would movechangeRootout from under a sync that is still reading it, leaving the change archived and the main specs never updated. If your agent can only run it by delegation, delegate synchronously and wait for the result.If the sync reports any stop or blocking condition, treat the sync as failed. Stop the archive immediately. Do not perform the post-sync content comparison and do not move its
changeRoot. Nothing has moved, so the user can fix the blocking condition or re-run the sync.After the sync writes each main spec, verify its structure against the canonical sync contract:
- A new main spec starts with a
# <capability> Specificationtitle. An existing main spec keeps its title exactly as it is. - Preserve existing
## Purposesections completely untouched for established main specs. - For a new main spec, copy the delta
## Purposeverbatim. Warn only if the purpose text is shorter than standard validation expects. Do not regenerate or rewrite existing authored purpose. If no usable## Purposeis provided, use the existing TBD Purpose behavior and warning. - Verify that no delta-style section headers (
## ADDED Requirements,## MODIFIED Requirements,## REMOVED Requirements,## RENAMED Requirements) remain in the main spec, adhering strictly to the sync workflow formatting rules. - Requirement blocks the sync wrote or changed use
### Requirement:headings, and their scenarios use#### Scenario:headings, under the spec's## Requirementssection. Leave content the delta does not mention exactly as it is.
Then re-run the comparison from the top of this step, including the explicitly retired, missing-spec case, against every capability that has a delta spec in
artifactPaths.specs.existingOutputPaths— not only the ones the sync reports it touched. A successful sync leaves nothing left to apply, so each capability must now read as already synced:- ADDED requirements present
- MODIFIED requirements carrying the scenario and description changes named in the delta, with their other scenarios intact
- REMOVED requirements gone — and where this sync retired a capability (removed its last requirement, leaving
## Requirementsempty), its main spec deleted rather than left empty. - RENAMED requirements present under the new name and absent under the old one
If the sync failed, or any capability does not match, report what differs and stop — do not archive. Nothing has moved and
changeRootis intact, so the user can fix the mismatch or re-run the sync and start the archive again.- Compare each delta spec with its corresponding main spec at
Perform the archive
Create an
archivedirectory underplanningHome.changesDirif it doesn't exist:mkdir -p "<planningHome.changesDir>/archive"Generate the target name: use the change name as-is when it already starts with a
YYYY-MM-DD-prefix; otherwise prepend the current date asYYYY-MM-DD-<change-name>. Never stack a second date (same rule asopenspec archive).Check if target already exists:
- If yes: Fail with error, suggest renaming existing archive or using different date
- If no: Move
changeRootto the archive directory
mv "<changeRoot>" "<planningHome.changesDir>/archive/<target-name>"Display summary
Show archive completion summary including:
- Change name
- Schema that was used
- Archive location
- Whether specs were synced (if applicable)
- Note about any warnings (incomplete artifacts/tasks)
Output On Success
## Archive Complete
**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** the archive path derived from `planningHome.changesDir`/<target-name>/
**Specs:** <"✓ Synced to main specs" only if the step 4 verification passed; otherwise "No delta specs" or "Sync skipped">
<"All artifacts complete. All tasks complete." — or, if archived with warnings, list them instead (e.g. "Archived with 2 incomplete tasks")>
Guardrails
- Announce the selected change; prompt for selection when it is ambiguous
- Use artifact graph (openspec status --json) for completion checking
- Don't block archive on warnings - just inform and confirm
- Preserve .openspec.yaml when moving to archive (it moves with the directory)
- Show clear summary of what happened
- If sync is requested, run the
openspec-sync-specsworkflow inline (agent-driven) - Never archive while a spec sync is still in flight — run the sync inline and verify the main specs before moving
changeRoot - If delta specs exist, always run the sync assessment and show the combined summary before prompting
- Apply relevant runtime context and report conflicts; operation guidance remains advisory
- Consider every guidance entry and explain any inapplicable or conflicting advice
- Existing CLI checks, resolved paths, prompts, and command contracts are unchanged
- Artifact rules constrain only the specs being written and are never operation guidance
- Never copy runtime context, operation guidance, or artifact-rule text verbatim into output files