Repository navigation
Proposal: bundle related skills into a packaged skill structure #590
Description
The OpenSpec change lifecycle is currently exposed as ~10 separate skills (new, apply, verify, archive, etc.), even though they all belong to the same domain.
Proposal: consolidate them into a single, simply named openspec skill that internally routes to the appropriate action (apply, continue, archive, ff, etc.).
This follows the same idea as the packaged approach used in Vercel’s react-best-practice skill:
https://github.com/vercel-labs/agent-skills/tree/main/skills/react-best-practice
There’s another small issue: some skills reference or instruct users to run commands like 'run /opsx:apply'. In this setup, that’s redundant and potentially confusing.
Skills already inject the required context and behavior when invoked. Since the logic was moved from AGENTS.md into skills, references should point to the skill itself, not to a command. In practice, in Claude /skill works the same way as /opsx, so mentioning commands here doesn’t add value.
Activity
clay-good commentedon Aug 6, 2026
Thanks for raising this, @evilsamaritan 🙏
This is about Consolidate the ~10 separate lifecycle skills into one
openspecskill that routes internally; drop/opsx:command references inside skills. — an open-ended feature/design idea rather than a discrete, PR-actionable bug or task. To honor it properly we've moved it to Discussions, where it can keep evolving with community input and you can re-engage anytime:👉 #1556
The original issue (and any comments) stays here for the record, so nothing is lost — please continue the conversation in the discussion above. Closing the issue in favor of that thread.