Move project description and tech stack research from CLAUDE.md into openspec/specs/project/ and openspec/specs/stack/. Slim CLAUDE.md to a pointer file. Populate config.yaml with project context. Add OpenSpec CLI skills and commands. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Why
CLAUDE.md currently holds all project knowledge — description, constraints, and a large tech stack research block. With OpenSpec initialized, this content belongs in openspec/specs/ where it can be managed as proper specs, referenced by changes, and won't conflict with CLAUDE.md's role as a slim workflow/instruction file.
What Changes
- Extract project description and constraints into a
projectspec - Extract full technology stack research into a
stackspec - Populate
openspec/config.yamlwith project context - Slim CLAUDE.md down to workflow instructions with pointers to OpenSpec
- Remove stale GSD placeholder sections (conventions, architecture, profile)
Capabilities
New Capabilities
project: Project identity, core value statement, and non-negotiable constraintsstack: Technology stack decisions — packages, versions, alternatives, patterns, compatibility, and sources
Modified Capabilities
Impact
CLAUDE.md: Reduced from ~147 lines to a slim pointer fileopenspec/specs/project/spec.md: New file with project identityopenspec/specs/stack/spec.md: New file with stack researchopenspec/config.yaml: Updated with project context