# superpowers changelog

> An agentic skills framework & software development methodology that works.

- Vendor: obra
- Category: AI
- Official site: https://github.com/obra/superpowers
- Tracked by: What's New (https://whatsnew.fyi/product/superpowers)
- Harvested from: GitHub (obra/superpowers)
- Entries below: 10 (newest first)

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

## Releases

### v6.2.0

- Date: 2026-07-24
- Version: v6.2.0
- Original notes: https://github.com/obra/superpowers/releases/tag/v6.2.0
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v6.2.0

- **changed** — The workspace is now plan-scoped: .superpowers/sdd/ resolves to a per-plan directory .superpowers/sdd/<plan-basename>/, sdd-workspace requires the plan file, task-brief and review-package write into their plan's directory, the ledger names its plan on its first line, and the workspace is deleted once the final review is clean
- **changed** — The review-fix loop now resumes the implementer with resume-the-implementer semantics instead of fresh dispatches, includes a scoped re-review prompt so the re-reviewer checks the fixes rather than re-reading the whole task, and installs a five-round circuit breaker with controller adjudication when it trips
- **changed** — testing-anti-patterns.md is renamed to writing-good-tests.md and rebuilt as a positive catalog with six rules, a falsifiability discipline including naming production changes that would fail the test, and a closing mutation check
- **changed** — TDD's Why Order Matters section is removed but its prose rebuttals survive as rationalization rows in the Common Rationalizations table
- **changed** — finishing-a-development-branch no longer offers to discard work in the completion menu; discard survives only as an explicit-request-only path with typed-confirmation ritual
- **changed** — Recap and persuasion prose removed from brainstorming, systematic-debugging, dispatching-parallel-agents, verification-before-completion, executing-plans, subagent-driven-development, requesting-code-review, receiving-code-review, using-git-worktrees, writing-plans, and writing-skills
- **changed** — PR creation is now forge-agnostic, using your forge's CLI or the URL printed on push instead of a blessed list of tools
- **changed** — The SessionStart hook now dispatches via Git Bash by declaring shell: bash, which Claude Code ≥ 2.1.81 resolves to Git for Windows directly and surfaces an actionable install prompt when Git Bash is missing
- **added** — Gemini CLI support is restored with install docs and the gemini-tools.md tool-mapping reference
- **fixed** — find-polluster.sh now correctly matches test files by fixing the ./ prefix mismatch in the -path pattern, preventing double-prefixing when a caller-supplied pattern includes the prefix, and handling **/ patterns that were silently skipping tests directly under the base directory
- **fixed** — The worktree path in finishing-a-development-branch is no longer recomputed after cleanup has changed directory, fixing a bug where provenance checks never matched and cleanup silently no-oped

##### v6.2.0 (2026-07-23)

###### Subagent-Driven Development

Two structural changes to how SDD tracks progress and closes out review findings, both developed against live eval campaigns.

- **The workspace is now plan-scoped.** `.superpowers/sdd/` had no plan identity and no end-of-life: a follow-up plan in the same working tree could read the previous plan's ledger as its own progress (observed in the wild, with multiple contamination rounds and ad-hoc workarounds). `sdd-workspace` now requires the plan file and resolves a per-plan directory, `.superpowers/sdd/<plan-basename>/`; `task-brief` and `review-package` write into their plan's directory (`review-package` gains the plan file as its first argument); the ledger names its plan on its first line; and the workspace is deleted once the final review is clean — git history is the durable record. Baseline evals showed controllers already refused foreign ledgers, but at a cost of 6–13 tool calls of cross-plan git forensics per resume; plan-scoping makes the answer structural instead. (25/25 baseline and GREEN eval runs documented in `docs/specs/` and `docs/plans/`.)
- **The review-fix loop resumes the implementer.** The lifecycle restructure gives fix rounds resume-the-implementer semantics instead of fresh dispatches, adds a scoped re-review prompt (`re-review-prompt.md`) so the re-reviewer checks the fixes rather than re-reading the whole task, and installs a five-round circuit breaker with controller adjudication when it trips. SKILL.md reorganizes by lifecycle, and its Red Flags convert to the house rationalization-table form.

###### Skills

A branch-wide compression campaign: recap sections, social proof, and benefits-selling prose aimed at a reader who has already invoked the skill are gone, with every load-bearing argument folded into a rationalization-table row or moved to its point of use. Each cut was micro-tested with subagent probes, and the one cut that measurably degraded behavior was reworked rather than shipped.

- **`testing-anti-patterns.md` is now `writing-good-tests.md`.** The TDD reference doc is rebuilt as a positive catalog — six rules that lead with the GOOD example — and absorbs a falsifiability discipline: name the production change that would fail the test, derive expectations independently of the code under test, and a closing mutation check. It closes two holes by name: the string-presence trap (grep-style tests on scripts, skills, and prompts counterfeit falsifiability — the observable is behavior, never text) and the change-detector trap (a constant assertion can fail and still protect nothing), each with a hard stop in the gate function. Trivial code and human prose earn no test; the trigger broadens from "adding mocks" to any test writing.
- **TDD's "Why Order Matters" rebuttals survive as rationalization rows.** Deleting the section outright measurably degraded test-first behavior under "just write it, tests after" pressure (control 8/10 → treatment 5/10, corroborated on Claude and Codex), so each prose rebuttal now lives in its Common Rationalizations row — the section is gone but the arguments fire where an agent hits them mid-rationalization.
- **`finishing-a-development-branch` no longer offers to discard your work.** The completion menu dates from when throwing away branches was routine; "Discard this work" next to "Merge" advertised destroying finished, passing work. Discard survives as an explicit-request-only path with the same typed-confirmation ritual. The same pass made PR creation forge-agnostic (your forge's CLI or the URL printed on push, not a blessed list of tools) and fixed a real bug: the worktree path was recomputed after cleanup had already changed directory, so provenance checks never matched and cleanup silently no-oped.
- **Recap and persuasion prose removed across the library.** `brainstorming`, `systematic-debugging`, `dispatching-parallel-agents`, `verification-before-completion`, `executing-plans`, `subagent-driven

_[Truncated at 4000 characters — full notes: https://github.com/obra/superpowers/releases/tag/v6.2.0]_

### v6.1.1

- Date: 2026-07-02
- Version: v6.1.1
- Original notes: https://github.com/obra/superpowers/releases/tag/v6.1.1
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v6.1.1

- **fixed** — Codex no longer re-registers the Claude SessionStart hook by declaring an explicit empty hooks object in the manifest
- **removed** — Remove orphaned Codex session-start dead code in hooks/session-start-codex and its test cases
- **changed** — Move worked shell-hook example in docs/porting-to-a-new-harness.md from Codex to Cursor
- **fixed** — Correct stale hooks-codex.json pointer in docs/windows/polyglot-hooks.md
- **fixed** — Fix the Codex plugin category to Developer Tools
- **added** — Add package-codex-plugin.sh script for building deterministic Codex portal packages with timestamp normalization, executable mode preservation, OpenAI metadata verification, and dirty worktree detection

##### v6.1.1 (2026-07-02)

###### Codex

- **Codex no longer re-registers the Claude SessionStart hook.** v6.1.0 removed the Codex hook config and its manifest `hooks` pointer, meaning to stop Codex from installing a SessionStart hook — but with no `hooks` field, Codex fell back to auto-discovering `hooks/hooks.json`, the Claude Code SessionStart hook that the marketplace ships from the repo root, and re-registered it along with its install-time trust prompt. The Codex manifest now declares an explicit empty hooks object (`hooks: {}`), which Codex reads as "no hooks" instead of reaching the auto-discovery fallback. An absent field, `[]`, and an empty inline list all collapse back to the fallback, so the value has to be exactly `{}`.
- **Removed orphaned Codex session-start dead code.** `hooks/session-start-codex` had no caller once the Codex hook config was deleted, so it and its redundant test cases are gone. The worked shell-hook example in `docs/porting-to-a-new-harness.md` moves from Codex — now native skill discovery with no session-start hook — to Cursor, a live shell-hook harness, and the stale `hooks-codex.json` pointer in `docs/windows/polyglot-hooks.md` is corrected. The Codex plugin category is also fixed to "Developer Tools".

###### Packaging

- **New `package-codex-plugin.sh` for building the Codex portal package.** A maintainer script produces a deterministic Codex "portal" archive — `.zip` by default, `tar.gz` on request — that normalizes entry timestamps, preserves executable modes, verifies every packaged skill ships its OpenAI metadata, includes the app and composer icons, and refuses to run against a dirty worktree. The packaged manifest keeps the source `hooks: {}` object so a portal-installed plugin avoids the same SessionStart auto-discovery, and the script can rebuild a byte-identical archive from a saved metadata source. Covered by a new test suite.

### v6.1.0

- Date: 2026-06-30
- Version: v6.1.0
- Original notes: https://github.com/obra/superpowers/releases/tag/v6.1.0
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v6.1.0

- **changed** — Compressed the using-superpowers bootstrap by replacing the graphviz skill-flow diagram with prose, folding the Instruction-Priority section into User Instructions, dropping the per-platform How to Access Skills walkthrough, and trimming the Platform Adaptation pointer
- **changed** — Pruned per-harness tool-mapping references to retain only harness-specific notes such as subagent dispatch, task tracking, and instructions-file paths
- **removed** — Deleted claude-code-tools.md and copilot-tools.md reference files as they contained no harness-specific content
- **added** — Codex can now install from the marketplace with a repo-local Codex marketplace manifest at .agents/plugins/marketplace.json
- **removed** — Codex no longer ships a SessionStart hook; removed hooks-codex.json config and its manifest registration
- **removed** — Removed Gemini CLI support following Google's EOL on 2026-06-18; Gemini is removed from install docs, subagent-capable platform lists, eval-harness description, and its tool-mapping reference is deleted

###### Lower Per-Session Token Cost

The `using-superpowers` bootstrap is injected into every session, so its size is paid for constantly. This release trims it and the per-harness references it points to, without dropping behavior-shaping content.

- **Compressed the `using-superpowers` bootstrap.** Replaced the graphviz skill-flow diagram with the prose it encoded, folded the standalone Instruction-Priority section into User Instructions, dropped the per-platform "How to Access Skills" walkthrough, and trimmed the Platform Adaptation pointer to the harnesses that still ship a reference file. The full Red Flags rationalization table and the user-instruction precedence rules are unchanged.
- **Pruned the per-harness tool-mapping references.** The verbose action-to-tool tables restated guidance modern agents already follow. Each reference file is trimmed to the harness-specific notes that still carry weight — subagent dispatch, task tracking, instructions-file paths — and `claude-code-tools.md` and `copilot-tools.md`, which had nothing harness-specific left, are deleted.

###### Codex

- **Codex can install from the marketplace.** Codex marketplace sources expect a `.agents/plugins/marketplace.json` at the marketplace root; the repo only shipped the Claude marketplace file, so Codex could name the marketplace but found no installable plugin entries. A repo-local Codex marketplace manifest now points at the same repository root, so the plugin is installable from Codex.
- **Codex no longer ships a SessionStart hook.** Codex reliably triggers skills on its own, and the bootstrap hook made the UX worse rather than better. The Codex hook config (`hooks-codex.json`) and its manifest registration are removed.

###### Harness Support

- **Gemini CLI support removed.** Google EOLed the Gemini CLI on 2026-06-18; the extension can no longer be installed or updated. Gemini is gone from the install docs, the subagent-capable platform lists, and the eval-harness description, and its tool-mapping reference is deleted.

### v6.0.3

- Date: 2026-06-18
- Version: v6.0.3
- Original notes: https://github.com/obra/superpowers/releases/tag/v6.0.3
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v6.0.3

- **changed** — SDD scratch files moved from .git/ to .superpowers/sdd/ directory to avoid Claude Code protection conflicts
- **added** — sdd-workspace helper to resolve SDD workspace per worktree
- **changed** — .superpowers/sdd/ directory is git-ignored and kept out of git status and commits

###### Subagent-Driven Development

- **SDD scratch files moved out of `.git/`.** Claude Code treats `.git/` as a protected path and denies agent writes there, so an implementer subagent writing its report into `.git/sdd/` got blocked mid-run. Task briefs, implementer reports, review diffs, and the progress ledger now live in a self-ignoring `.superpowers/sdd/` directory in the working tree — kept out of `git status` and out of commits, and resolved per worktree by a shared `sdd-workspace` helper. One caveat: because the workspace is git-ignored working-tree scratch, `git clean -fdx` will delete the progress ledger; recover from `git log` if that happens. (#1780)

### v6.0.2

- Date: 2026-06-17
- Version: v6.0.2
- Original notes: https://github.com/obra/superpowers/releases/tag/v6.0.2
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v6.0.2

- **removed** — Remove the evals submodule from the shipped plugin as it broke plugin installs for some users

###### Install Fixes

- **We no longer ship the `evals` submodule.** It broke plugin installs for some users, so the eval harness now lives in its own repo, separate from the published plugin. (#1778, #1774)

### v6.0.0

- Date: 2026-06-16
- Version: v6.0.0
- Original notes: https://github.com/obra/superpowers/releases/tag/v6.0.0
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v6.0.0

- **changed** — Rewrite of subagent-driven-development task review system to use a single reviewer per task instead of two, reducing token usage by approximately 50% and improving speed
- **changed** — Replace separate spec-reviewer-prompt.md and code-quality-reviewer-prompt.md files with a single task-reviewer-prompt.md file
- **changed** — Move worktrees from global ~/.config/superpowers/worktrees/ directory to project-local .worktrees/ directory
- **added** — Add support for Kimi Code harness with plugin manifest and marketplace installation
- **added** — Add support for Pi harness as a session-start extension with native skills
- **added** — Add support for Antigravity harness with direct plugin installation and bootstrap from first message
- **added** — Implement pre-flight plan validation to check for internal conflicts before the first task
- **added** — Add task-brief and review-package scripts to write task text and review diffs as files instead of pasted text
- **added** — Add Global Constraints block to plans to list rules that bind every task
- **added** — Add per-task Interfaces block to plans to specify what each task consumes and produces
- **added** — Implement single whole-branch review at end of run on the most capable model instead of re-reviewing task by task
- **changed** — Make reviewer prompts read-only and prevent reviewers from modifying the working tree or branch
- **changed** — Require explicit model specification for every dispatch instead of allowing unnamed models to inherit the session's most expensive model
- **changed** — Ban controller ability to suppress findings or pre-rate severity in reviewer judgments
- **changed** — Add file and line evidence backing to reviewer answers and progress ledger for resuming interrupted work
- **changed** — Rewrite skills' tool calls to be significantly more vendor-neutral
- **changed** — Improve brainstorming visual companion security model with authentication
- **changed** — Improve brainstorming visual companion to survive restarts and dropped connections

##### v6.0.0 (2026-06-16)

Superpowers 6.0 is a big release. The headline is a rewrite of how `subagent-driven-development` reviews each task — cheaper, stricter, and harder to game. 

While these numbers won't hold on every harness and for every workload, in our evals, Claude Code and Codex produce similar high-quality results roughly twice as fast and while spending almost 50% fewer tokens.

It also adds three new harnesses (Kimi Code, Pi, and Antigravity), gives the brainstorming visual companion a better security model, and rewrites a number of skills' tool calls to be significantly more vendor-neutral.

###### Visible Changes

- **The two per-task reviewer prompts became one.** `spec-reviewer-prompt.md` and `code-quality-reviewer-prompt.md` are gone, replaced by a single `task-reviewer-prompt.md`. If you dispatch the old files directly, switch to the new one.
- **The legacy global worktree directory is gone.** `using-git-worktrees` and `finishing-a-development-branch` no longer use `~/.config/superpowers/worktrees/`. Worktrees now land in the project — an existing `.worktrees/` or `worktrees/` if you have one, otherwise a fresh `.worktrees/` — unless you say otherwise.

###### New Harness Support

Superpowers now runs on three more harnesses. Each ships its own bootstrap, a tool-mapping reference, and tests, and each gets its own install section in the README.

- **Kimi Code** — a plugin manifest, install docs, and manifest tests; install from Kimi's marketplace or straight from the repo. (initial manifest by @qer)
- **Pi** — a session-start extension that registers the skills and injects the `using-superpowers` bootstrap. Pi has native skills, so it needs no compatibility shim.
- **Antigravity (`agy`)** — installs the plugin directly and bootstraps from the first message; verified end-to-end against the standard "make a react todo list" acceptance test.

###### Subagent-Driven Development

A long run of cost-and-quality experiments on real projects reshaped how the controller reviews each task. The old flow ran two reviewers per task and leaned on the controller's judgment for model choice and severity, and both turned out to be expensive and easy to game. The new flow runs one reviewer per task, hands work off as files instead of pasted text, and takes several judgment calls away from the controller.

- **One reviewer per task, two verdicts.** A single `task-reviewer-prompt.md` reads the task's diff once and returns both a spec-compliance verdict and a quality verdict, so one fix pass clears both. A new "can't verify from the diff" verdict flags requirements that live in untouched code, for the controller to check itself. (#1538, #1543)
- **One broad review at the end.** The run finishes with a single whole-branch review on the most capable model, instead of re-reviewing everything task by task.
- **Plans get a pre-flight read.** Before the first task, the controller checks the plan for internal conflicts — and for anything the plan asks for that a reviewer would flag as a defect — and raises it all at once, rather than stumbling into it mid-run.
- **Diffs and task text move as files.** A pasted diff parks itself permanently in the most expensive context, and a reviewer without one rebuilds it by hand — the single biggest reviewer cost. Two new scripts, `task-brief` and `review-package`, write the task text and the review diff to files for the subagent to read.
- **Every dispatch states its model.** Left to choose, controllers stopped naming a model at all — and an unnamed model quietly inherits the session's most expensive one, so one run put all 26 of its reviewers on the top tier. The templates now require a model, with guidance that reaches for cheaper tiers when the work allows.
- **The controller can't tell a reviewer what to ignore.** Real runs caught controllers coaching reviewers to skip a finding or call it "Minor at most," and the flaw shipped. Suppressing findings and pre-rating severity are now banned outri

_[Truncated at 4000 characters — full notes: https://github.com/obra/superpowers/releases/tag/v6.0.0]_

### v5.1.0

- Date: 2026-05-04
- Version: v5.1.0
- Original notes: https://github.com/obra/superpowers/releases/tag/v5.1.0
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v5.1.0

- **removed** — Legacy slash commands /brainstorm, /execute-plan, and /write-plan have been removed; use superpowers:brainstorming, superpowers:executing-plans, and superpowers:writing-plans directly instead
- **removed** — superpowers:code-reviewer named agent has been removed; dispatch Task (general-purpose) with the prompt template from skills/requesting-code-review/code-reviewer.md instead
- **removed** — Integration sections have been removed from skills
- **changed** — using-git-worktrees and finishing-a-development-branch skills now detect when the agent is running inside an isolated worktree and prefer the harness's native worktree controls before falling back to git worktree
- **added** — Environment detection checks GIT_DIR != GIT_COMMON to determine if already in a linked worktree, with a submodule guard to prevent false detection
- **changed** — using-git-worktrees no longer creates worktrees implicitly and now asks the user for consent before creating worktrees
- **added** — Native tool preference in worktree skills: when the harness exposes its own worktree tool, the skill defers to it and respects the user's stated preference
- **fixed** — finishing-a-development-branch only cleans up worktrees inside .worktrees/ created by superpowers, leaving external worktrees untouched
- **changed** — Detached HEAD handling in the finishing menu now collapses to two options when there is no branch to merge from
- **fixed** — Hardcoded /Users/jesse paths in skill examples replaced with generic placeholders
- **added** — Two new sections added to CLAUDE.md for AI agents covering pre-submission checklist and unacceptable contribution types
- **added** — New harness PRs now require a session transcript demonstrating the acceptance test with auto-triggered brainstorming in a clean session
- **added** — New sync-to-codex-plugin script mirrors superpowers into the OpenAI Codex plugin marketplace as prime-radiant-inc/openai-codex-plugins with path/user-agnostic operation
- **fixed** — Bootstrap content is now cached at module level in OpenCode, eliminating repeated fs.existsSync and fs.readFileSync calls on every agent step
- **added** — requesting-code-review skill is now self-contained with persona and checklist in skills/requesting-code-review/code-reviewer.md dispatching Task (general-purpose) directly
- **changed** — subagent-driven-development now dispatches Task (general-purpose) instead of the named code-reviewer agent

###### Removals

- **Legacy slash commands removed** — `/brainstorm`, `/execute-plan`, and `/write-plan` are gone. They were deprecated stubs that did nothing but tell the user to invoke the corresponding skill. Invoke `superpowers:brainstorming`, `superpowers:executing-plans`, and `superpowers:writing-plans` directly instead. (#1188)
- **`superpowers:code-reviewer` named agent removed** — the agent was the plugin's only named agent and was used by exactly two skills, while every other reviewer/implementer subagent in the repo dispatches `general-purpose` with a prompt template alongside its skill. The agent's persona and checklist have been merged into `skills/requesting-code-review/code-reviewer.md` as a self-contained Task-dispatch template. Anyone dispatching `Task (superpowers:code-reviewer)` should switch to `Task (general-purpose)` with the prompt template instead. (PR #1299)
- **Integration sections removed from skills** — these were a legacy of the time before agents had native skills systems and didn't help with steering.

###### Worktree Skills Rewrite

`using-git-worktrees` and `finishing-a-development-branch` now detect when the agent is already running inside an isolated worktree and prefer the harness's native worktree controls before falling back to `git worktree`. Behavior was TDD-validated and cross-platform-checked across five harnesses. (PRI-974, PR #1121)

- **Environment detection** — both skills check `GIT_DIR != GIT_COMMON` before doing anything; if already in a linked worktree, creation is skipped entirely. A submodule guard prevents false detection.
- **Consent before creating worktrees** — `using-git-worktrees` no longer creates worktrees implicitly; the skill asks the user first. Fixes #991 (subagent-driven-development was auto-creating worktrees without consent).
- **Native tool preference (Step 1a)** — when the harness exposes its own worktree tool (e.g. Codex), the skill defers to it. The user's stated preference is respected when expressed.
- **Provenance-based cleanup** — `finishing-a-development-branch` only cleans up worktrees inside `.worktrees/` (created by superpowers); anything outside is left alone. Fixes #940 (Option 2 was incorrectly cleaning up worktrees), #999 (merge-then-remove ordering), and #238 (`cd` to repo root before `git worktree remove`).
- **Detached HEAD handling** — the finishing menu collapses to two options when there is no branch to merge from.
- **Hardcoded `/Users/jesse` paths** in skill examples replaced with generic placeholders. (#858, PR #1122)

###### Contributor Guidelines for AI Agents

Two new sections at the top of `CLAUDE.md` (symlinked to `AGENTS.md`) speak directly to AI agents. An audit of the last 100 closed PRs against this repo showed a 94% rejection rate driven by AI-generated slop: agents that didn't read the PR template, opened duplicates, fabricated problem descriptions, or pushed fork- or domain-specific changes upstream.

- **Pre-submission checklist** — read the PR template, search for existing PRs, verify a real problem exists, confirm the change belongs in core, and show the human partner the complete diff before submitting.
- **What we will not accept** — third-party dependencies, "compliance" rewrites of skill content, project-specific configuration, bulk PRs, speculative fixes, domain-specific skills, fork-specific changes, fabricated content, and bundled unrelated changes.
- **New harness PRs require a session transcript** — most past new-harness integrations copied skill files or wrapped with `npx skills` instead of loading the `using-superpowers` bootstrap at session start. The acceptance test ("Let's make a react todo list" must auto-trigger `brainstorming` in a clean session) and a complete transcript are now required.

###### Codex Plugin Mirror Tooling

New `sync-to-codex-plugin` script mirrors superpowers into the OpenAI Codex plugin marketplace as `prime-radiant-inc/openai-codex-plugins`. Path/user-agnostic so any team member can

_[Truncated at 4000 characters — full notes: https://github.com/obra/superpowers/releases/tag/v5.1.0]_

### v5.0.7

- Date: 2026-03-31
- Version: v5.0.7
- Original notes: https://github.com/obra/superpowers/releases/tag/v5.0.7
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v5.0.7

- **added** — Session-start hook now detects the COPILOT_CLI environment variable and emits SDK-standard additionalContext format for Copilot CLI support
- **added** — Added references/copilot-tools.md with Claude Code to Copilot CLI tool equivalence table
- **added** — Added Copilot CLI to the using-superpowers skill's platform instructions and README installation section
- **fixed** — Bootstrap text no longer advertises misleading configDir/skills/superpowers/ path and uses native skill tool instead
- **changed** — Moved bootstrap injection from experimental.chat.system.transform to experimental.chat.messages.transform, prepending to the first user message instead of adding a system message

##### GitHub Copilot CLI Support

- **SessionStart context injection** — Copilot CLI v1.0.11 added support for `additionalContext` in sessionStart hook output. The session-start hook now detects the `COPILOT_CLI` environment variable and emits the SDK-standard `{ "additionalContext": "..." }` format, giving Copilot CLI users the full superpowers bootstrap at session start.
- **Tool mapping** — added `references/copilot-tools.md` with the full Claude Code to Copilot CLI tool equivalence table
- **Skill and README updates** — added Copilot CLI to the `using-superpowers` skill's platform instructions and README installation section

##### OpenCode Fixes

- **Skills path consistency** — the bootstrap text no longer advertises a misleading `configDir/skills/superpowers/` path that didn't match the runtime path. The agent should use the native `skill` tool, not navigate to files by path. Tests now use consistent paths derived from a single source of truth. (#847, #916)
- **Bootstrap as user message** — moved bootstrap injection from `experimental.chat.system.transform` to `experimental.chat.messages.transform`, prepending to the first user message instead of adding a system message. Avoids token bloat from system messages repeated every turn (#750) and fixes compatibility with Qwen and other models that break on multiple system messages (#894).

### v5.0.6

- Date: 2026-03-25
- Version: v5.0.6
- Original notes: https://github.com/obra/superpowers/releases/tag/v5.0.6
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v5.0.6

- **changed** — Replace subagent review loops in brainstorming with inline Spec Self-Review checklist covering placeholder scan, internal consistency, scope check, and ambiguity check
- **changed** — Replace Plan Review Loop in writing-plans with inline Self-Review checklist covering spec coverage, placeholder scan, and type consistency
- **added** — Add explicit "No Placeholders" section in writing-plans defining plan failures as TBD, vague descriptions, undefined references, and references similar to Task N
- **changed** — Restructure brainstorm server session directory to separate content/ and state/ subdirectories, with both screen_dir and state_dir paths included in server-started JSON
- **fixed** — Fix brainstorm server owner-PID monitoring false shutdowns by treating EPERM as alive and validating owner PID at startup to disable monitoring if already dead
- **removed** — Remove Windows/MSYS2-specific carve-out from start-server.sh
- **fixed** — Correct writing-skills documentation to say SKILL.md frontmatter supports two required fields and link to agentskills.io specification
- **added** — Add named agent dispatch mapping documenting translation from Claude Code's named agent types to Codex spawn_agent with worker roles
- **added** — Add environment detection and Codex App finishing sections for worktree-aware skills
- **added** — Add Codex App compatibility design spec covering read-only environment detection, worktree-safe skill behavior, and sandbox fallback patterns

###### Inline Self-Review Replaces Subagent Review Loops

The subagent review loop (dispatching a fresh agent to review plans/specs) doubled execution time (~25 min overhead) without measurably improving plan quality. Regression testing across 5 versions with 5 trials each showed identical quality scores regardless of whether the review loop ran.

- **brainstorming** — replaced Spec Review Loop (subagent dispatch + 3-iteration cap) with inline Spec Self-Review checklist: placeholder scan, internal consistency, scope check, ambiguity check
- **writing-plans** — replaced Plan Review Loop (subagent dispatch + 3-iteration cap) with inline Self-Review checklist: spec coverage, placeholder scan, type consistency
- **writing-plans** — added explicit "No Placeholders" section defining plan failures (TBD, vague descriptions, undefined references, "similar to Task N")
- Self-review catches 3-5 real bugs per run in ~30s instead of ~25 min, with comparable defect rates to the subagent approach

###### Brainstorm Server

- **Session directory restructured** — the brainstorm server session directory now contains two peer subdirectories: `content/` (HTML files served to the browser) and `state/` (events, server-info, pid, log). Previously, server state and user interaction data were stored alongside served content, making them accessible over HTTP. The `screen_dir` and `state_dir` paths are both included in the server-started JSON. (Reported by 吉田仁)

###### Bug Fixes

- **Owner-PID lifecycle fixes** — the brainstorm server's owner-PID monitoring had two bugs causing false shutdowns within 60 seconds: (1) EPERM from cross-user PIDs (Tailscale SSH, etc.) was treated as "process dead", and (2) on WSL the grandparent PID resolves to a short-lived subprocess that exits before the first lifecycle check. Fixed by treating EPERM as "alive" and validating the owner PID at startup — if it's already dead, monitoring is disabled and the server relies on the 30-minute idle timeout. This also removes the Windows/MSYS2-specific carve-out from `start-server.sh` since the server now handles it generically. (#879)
- **writing-skills** — corrected false claim that SKILL.md frontmatter supports "only two fields"; now says "two required fields" and links to the agentskills.io specification for all supported fields (PR #882 by @arittr)

###### Codex App Compatibility

- **codex-tools** — added named agent dispatch mapping documenting how to translate Claude Code's named agent types to Codex's `spawn_agent` with worker roles (PR #647 by @arittr)
- **codex-tools** — added environment detection and Codex App finishing sections for worktree-aware skills (by @arittr)
- **Design spec** — added Codex App compatibility design spec (PRI-823) covering read-only environment detection, worktree-safe skill behavior, and sandbox fallback patterns (by @arittr)

### v5.0.5

- Date: 2026-03-17
- Version: v5.0.5
- Original notes: https://github.com/obra/superpowers/releases/tag/v5.0.5
- Permalink: https://whatsnew.fyi/product/superpowers/releases/v5.0.5

- **fixed** — Rename server.js to server.cjs so the brainstorming server starts correctly on Node.js 22+ where the root package.json "type": "module" caused require() to fail
- **fixed** — Skip PID lifecycle monitoring on Windows/MSYS2 where the PID namespace is invisible to Node.js, preventing the server from self-terminating after 60 seconds
- **fixed** — Verify the server process actually died before reporting success with SIGTERM + 2s wait + SIGKILL fallback in stop-server.sh
- **changed** — Restore user choice between subagent-driven and inline execution after plan writing

##### Bug Fixes

- **Brainstorm server ESM fix** — renamed `server.js` → `server.cjs` so the brainstorming server starts correctly on Node.js 22+ where the root `package.json` `"type": "module"` caused `require()` to fail. (PR #784 by @sarbojitrana, fixes #774, #780, #783)
- **Brainstorm owner-PID on Windows** — skip PID lifecycle monitoring on Windows/MSYS2 where the PID namespace is invisible to Node.js, preventing the server from self-terminating after 60 seconds. (#770, docs from PR #768 by @lucasyhzlu-debug)
- **stop-server.sh reliability** — verify the server process actually died before reporting success. SIGTERM + 2s wait + SIGKILL fallback. (#723)

##### Changed

- **Execution handoff** — restore user choice between subagent-driven and inline execution after plan writing. Subagent-driven is recommended but no longer mandatory.