From c0d485c159f82465340e7895eef428cfe6d48540 Mon Sep 17 00:00:00 2001 From: Clay Good Date: Wed, 5 Aug 2026 15:18:38 -0500 Subject: [PATCH 1/2] chore(release): add catch-up changeset for Rovo, Codex dir, status Cover three user-facing PRs that merged without changesets so they appear in the v1.8.0 CHANGELOG: - #1516 Atlassian Rovo Dev CLI (new tool) - #1511 Codex skills move to shared .agents directory - #1505 openspec status separates planning from implementation Co-Authored-By: Claude Opus 4.8 --- .changeset/catch-up-rovo-codex-status.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 .changeset/catch-up-rovo-codex-status.md diff --git a/.changeset/catch-up-rovo-codex-status.md b/.changeset/catch-up-rovo-codex-status.md new file mode 100644 index 0000000000..e587dd1e43 --- /dev/null +++ b/.changeset/catch-up-rovo-codex-status.md @@ -0,0 +1,12 @@ +--- +"@fission-ai/openspec": minor +--- + +### New Features + +- **Atlassian Rovo Dev CLI** — `openspec init --tools rovodev` installs the OpenSpec workflow skills for Atlassian's Rovo Dev CLI. It is skills-only (no slash commands), written to `.rovodev`. + +### Bug Fixes + +- **Codex skills now live in the shared `.agents` directory** — `openspec init` and `openspec update` install Codex skills under `.agents/skills/` (the canonical location assistants read) and migrate an existing `.codex` skills directory in place. Files you customized are preserved, not overwritten. +- **`openspec status` separates planning from implementation** — status now reports `isPlanningComplete` (every planning artifact is written) distinctly from overall progress, and its messages no longer imply a change is finished before it has been implemented. `isComplete` is kept as a compatibility alias, so existing scripts keep working. From 5fc02e923cae76d785d968c0b7508ad43287c4e0 Mon Sep 17 00:00:00 2001 From: Clay Good Date: Wed, 5 Aug 2026 15:28:46 -0500 Subject: [PATCH 2/2] chore(release): correct isPlanningComplete wording in changeset Skipped planning artifacts count as satisfied without being written; say "every non-skipped planning artifact exists" to match the CLI and agent-contract docs (alfred/CodeRabbit review). Co-Authored-By: Claude Opus 4.8 --- .changeset/catch-up-rovo-codex-status.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.changeset/catch-up-rovo-codex-status.md b/.changeset/catch-up-rovo-codex-status.md index e587dd1e43..b940e8e73e 100644 --- a/.changeset/catch-up-rovo-codex-status.md +++ b/.changeset/catch-up-rovo-codex-status.md @@ -9,4 +9,4 @@ ### Bug Fixes - **Codex skills now live in the shared `.agents` directory** — `openspec init` and `openspec update` install Codex skills under `.agents/skills/` (the canonical location assistants read) and migrate an existing `.codex` skills directory in place. Files you customized are preserved, not overwritten. -- **`openspec status` separates planning from implementation** — status now reports `isPlanningComplete` (every planning artifact is written) distinctly from overall progress, and its messages no longer imply a change is finished before it has been implemented. `isComplete` is kept as a compatibility alias, so existing scripts keep working. +- **`openspec status` separates planning from implementation** — status now reports `isPlanningComplete` (every non-skipped planning artifact exists; skipped artifacts count as satisfied without being written) distinctly from overall progress, and its messages no longer imply a change is finished before it has been implemented. `isComplete` is kept as a compatibility alias, so existing scripts keep working.