Init openspec & generate specs on existing codebase#168
Conversation
Reversean
left a comment
Reversean
left a comment
There was a problem hiding this comment.
Spec-driven development is a genuinely good direction, and I'd love to see this pattern spread to our other repos too.
Left a few line notes below on tightening things up.
I also wanted to point out that no CI step validates the specs (e.g. openspec validate). Is this planned for future changes?
| @@ -0,0 +1,160 @@ | |||
| --- | |||
There was a problem hiding this comment.
This file (and its counterparts under .opencode/skills/, plus the second copy under packages/.claude/skills/) duplicates .claude/skills/.
Skills follow the open Agent Skills standard, and all three tools already read .claude/skills/ or .agents/skills directly.
Claude Code also walks up to the repo root for skills, so the packages/.claude/skills copy isn't needed either. Recommend keeping just the root .claude/skills/ and dropping the ~21 duplicate files across .github/skills, .opencode/skills, and packages/.claude/skills.
Co-authored-by: Reversean <43142829+Reversean@users.noreply.github.com>
I am not sure we need it at this point. For now I'd assume the spec and implementation would be done by the same person in the same branch, so the change spec would be verified and archived before it gets to the main branch or even committed to the feature branch. Once we would be open to the community contributions we can think about that |
Documents setup, testing, and the OpenSpec-driven change workflow. Also removes packages/.claude, packages/.github, and packages/openspec, which were duplicate/misplaced files from running openspec tooling with the wrong working directory. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2 participants
No description provided.