Skip to content

Conversation

@TabishB
Copy link
Contributor

@TabishB TabishB commented Jan 25, 2026

OpenSpec 1.0 — The OPSX Release

The workflow has been rebuilt from the ground up.

Breaking Changes

  • Old /openspec:* commands removed
  • Config files (CLAUDE.md, .cursorrules, AGENTS.md, project.md) no longer generated
  • Run openspec init to upgrade

What Changed

Before After
Static prompts (same every time) Dynamic instructions (context + rules + template based on artifact state)
Phase-locked (proposal → apply → archive) Action-based (any action anytime, artifact graph tracks state)
Text-based spec merging Semantic syncing (ADDED/MODIFIED/REMOVED/RENAMED at requirement level)
8+ scattered config files Single .claude/skills/ directory (Agent Skills standard)
3 commands 10 commands including explore, verify, bulk-archive, onboard

New Commands

  • /opsx:explore — Think through ideas before committing
  • /opsx:new — Start a change
  • /opsx:continue — Create one artifact at a time (step-through)
  • /opsx:ff — Create all artifacts at once (fast-forward)
  • /opsx:apply — Implement tasks
  • /opsx:verify — Validate implementation matches artifacts
  • /opsx:sync — Sync delta specs to main specs
  • /opsx:archive — Archive completed change
  • /opsx:bulk-archive — Archive multiple changes with conflict detection
  • /opsx:onboard — Guided 15-minute walkthrough

New Features

  • Onboarding skill — 11-phase guided first experience with codebase-aware task suggestions
  • 21 AI tools — Claude, Cursor, Windsurf, Continue, Gemini, GitHub Copilot, Amazon Q, and 14 more
  • Interactive setup — Animated welcome screen + searchable multi-select
  • Customizable schemas — Define workflows in openspec/schemas/ without touching code

Bug Fixes

  • Claude Code YAML parsing failure with colons in names
  • Task file trailing whitespace handling
  • JSON instruction output separating context/rules from template

Documentation

  • New getting-started, CLI reference, concepts docs
  • Removed misleading mid-flight editing claims
  • Added migration guide

🤖 Generated with Claude Code

@greptile-apps
Copy link

greptile-apps bot commented Jan 25, 2026

No reviewable files after applying ignore patterns.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 25, 2026

📝 Walkthrough

Walkthrough

A changeset documentation file announcing the OPSX rebrand and comprehensive workflow rewrite for OpenSpec, including removal of legacy /openspec:* commands, introduction of new /opsx:* commands, semantic specification syncing at the requirement level, multi-provider AI tool support, and interactive onboarding.

Changes

Cohort / File(s) Summary
Changeset Documentation
.changeset/opsx-1.0.md
Declares OPSX rebrand with breaking changes (legacy command removal), new /opsx:* command suite (/new, /ff, /continue, /apply, /archive, /onboard), semantic spec syncing with requirement-level change tracking (ADDED/MODIFIED/REMOVED/RENAMED), multi-provider AI support (21 tools), Agent Skills metadata integration, and associated bug fixes and documentation updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 OPSX hops in with grace, a rebrand so bright,
Legacy commands fade as new workflows take flight,
Semantic specs sync, requirements shine clear,
Multi-tool harmony—the future is here!

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title states 'chore: add changeset for 1.0.0 release' but describes a v0.24.0 feature changeset with breaking changes including OPSX rebrand, workflow rewrite, command removals, and semantic spec syncing—not a routine 1.0.0 release chore. Update the title to accurately reflect the substantial nature of changes, such as 'feat!: add changeset for OPSX 1.0.0 rebrand and workflow rewrite' to convey the breaking changes and major feature overhaul.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@vibe-kanban-cloud
Copy link

Review Complete

Your review story is ready!

View Story

Comment !reviewfast on this PR to re-generate the story.

Update from minor to major version bump. Rewrite release notes to
properly capture the OPSX workflow changes:

- Dynamic instructions based on artifact state
- Semantic spec syncing with ADDED/MODIFIED/REMOVED parsing
- Step-through artifacts with /opsx:continue
- Skills support alongside tool commands
- Breaking: old /openspec:* commands removed
@TabishB TabishB changed the title chore: add changeset for v0.24.0 features chore: add changeset for 1.0.0 release Jan 25, 2026
Based on deep research into old vs new workflow:

Old workflow:
- 3 phase-locked commands (proposal → apply → archive)
- 8+ config files scattered at project root
- Static prompts, same instructions every time
- Text-based spec merging

New OPSX workflow:
- 10 action-based commands (do any action anytime)
- Dynamic instructions (context + rules + template layers)
- Artifact graph with dependency awareness
- Semantic spec syncing (ADDED/MODIFIED/REMOVED/RENAMED)
- Agent Skills standard for cross-editor compatibility
- 21 AI tools supported
- Onboarding skill for guided first experience
@TabishB
Copy link
Contributor Author

TabishB commented Jan 26, 2026

Recreating with correct branch name (changeset-1.0.0-opsx)

@TabishB TabishB closed this Jan 26, 2026
@TabishB TabishB deleted the changeset-v0.24.0-features branch January 26, 2026 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants