feat: add open spec#10914
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This pull request introduces comprehensive documentation for the experimental OPSX workflow commands and their corresponding Claude skills, covering the full lifecycle of proposing, exploring, applying, and archiving OpenSpec changes. The new markdown files provide step-by-step guidance, guardrails, and output examples for each workflow phase, ensuring clarity for both users and automation.
The most important changes are:
OPSX Workflow Command Documentation:
.claude/commands/opsx/propose.mdto document how to propose a new change, including artefact creation, dependency management, and user prompts for unclear requirements..claude/commands/opsx/apply.mddetailing the process for implementing tasks from an OpenSpec change, including task selection, progress tracking, and handling blockers or completion..claude/commands/opsx/archive.mddescribing how to archive a completed change, with checks for incomplete artefacts or tasks, delta spec synchronisation, and user confirmations..claude/commands/opsx/explore.mdto define "explore mode," focusing on investigation, brainstorming, and requirements clarification without implementation, including OpenSpec artefact awareness and guardrails.Claude Skill Integration:
.claude/skills/openspec-apply-change/SKILL.mdto specify the behaviour and guardrails for theopenspec-apply-changeskill, closely mirroring the documented workflow for applying OpenSpec changes.Linked issue
N/A
Changes
Checklist
index.d.tsandindex.d.cts)Summary by cubic
Adds an experimental
openspecworkflow with OPSX commands and skills to propose, explore, apply, and archive changes, plus a spec-drivenopenspec/config.yamlwith project context and rules. Also stops ignoring.claude,.opencode, andopenspec/so the workflow assets are tracked.Description
Summary of changes
.claude/commands/opsx/*and.opencode/commands/*for propose, explore, apply, and archive..claude/skills/*and.opencode/skills/*.openspec/config.yaml(schema: spec-driven) with project context, rules, and artifact guidance tailored toaxios..gitignoreto include.claude/,.opencode/, andopenspec/.Reasoning
openspecCLI.Additional context
.claudeand.opencodeto support different runtimes.openspecCLI JSON outputs for status/instructions.Docs
/docs/covering:openspecworkflow (propose → explore → apply → archive).openspec/config.yamlshapes artifacts and rules.Testing
openspec new change,openspec status --json, andopenspec instructions <artifact|apply> --jsonto validate paths, dependencies, and contextFiles..gitignorenow tracks.claude/,.opencode/, andopenspec/.Semantic version impact
Written for commit 8b494ee. Summary will update on new commits. Review in cubic