Add OpenSpec, Claude Code skills, and planning scaffolding#340
Merged
Conversation
Checks in the project-level tooling used for spec-driven feature work: - openspec/ — OpenSpec config and directories for change proposals and archived specs - .claude/commands/opsx — slash commands for the propose/apply/archive/explore workflow - .claude/skills/openspec-* — skill definitions invoked by those commands - .planning/ — feature spec drafts (per CLAUDE.md convention) .claude/settings.local.json is gitignored since it holds per-machine permissions allowlist that varies by contributor.
|
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
1 participant
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
openspec/— config and directories for spec-driven change proposals and archived specs.claude/commands/opsxand.claude/skills/openspec-*— slash commands and skill definitions for the propose / apply / archive / explore workflow.planning/— feature spec drafts (per the convention already documented inCLAUDE.md).claude/settings.local.jsonsince it holds per-machine permissions allowlist that varies by contributorNo runtime code is touched; this is tooling/scaffolding only.
Test plan
openspec statusruns against the committed config without errors/opsx:propose,/opsx:apply,/opsx:archive,/opsx:explore) resolve from the checked-in.claude/commands/opsx/*.md.claude/settings.local.jsonis not tracked after pulling this branch