|
|
@@ -1,5 +1,59 @@
|
|
|
# Superpowers Release Notes
|
|
|
|
|
|
+## v6.4.0 (2026-09-17)
|
|
|
+
|
|
|
+### New Skills
|
|
|
+
|
|
|
+- **`diagnosing-superpowers`**: when a session goes wrong (repeated work, an ignored plan, a skill that didn't fire, a surprising bill), ask your agent to "figure out what went wrong with superpowers in this session." It pins down the problem with you, reads the transcripts on disk, and reports what happened with `path:line` evidence for every finding. On request it builds a scrubbed bundle or drafts a GitHub issue for your approval; scrubbing keeps the cited evidence intact so a maintainer can verify the report. Works on the current session or a past one. (#2236, #2287)
|
|
|
+- **`proving-it-works-with-a-movie`**: record a demo, screencast, or proof video of software actually running. Four routes (browser motion, terminal, composited stills, a reel rendered from a run's own log), narration and subtitles, and a `check-movie` gate that catches the defects nobody notices until someone watches: a frozen picture, narration over a dead screen, dropped words. It never stages or reenacts a beat. Needs `uv` and `ffmpeg`; works on macOS, Linux, and native Windows. (#2214, #2275)
|
|
|
+
|
|
|
+### Executing Plans
|
|
|
+
|
|
|
+- **Inline execution is now a real mode.** `executing-plans` was a 64-line stub that measured the same as running with no plugin at all. It is rebuilt: the session implements every task itself under the same workspace, ledger, and stopping rules as subagent-driven development, then dispatches one fresh whole-branch review on the most capable model. `task-start` and `task-done` helpers keep the ledger and test log honest. It is the cheapest way to run a plan and runs well on a mid-tier session model. The old batch-with-human-checkpoints behavior is gone. (#2318)
|
|
|
+
|
|
|
+### Writing Plans
|
|
|
+
|
|
|
+- **You review the saved plan before anything runs.** Approving an idea or a scope no longer counts as approving a plan you haven't seen. (#2258)
|
|
|
+- **The execution handoff names two approaches, Subagent-driven and Native,** says what each costs, and recommends one for this plan with a reason drawn from the plan. If you already chose a method, it keeps your choice and asks only for the plan review. (#2258, #2318)
|
|
|
+- **Plans carry a Review Focus section**: the five inputs or failure modes the spec implies but no task's tests exercise, each pinned by a test in the task that owns the code. In evals every implementer shipped the same crash on an input the spec implied but never named. (#2319)
|
|
|
+
|
|
|
+### Brainstorming
|
|
|
+
|
|
|
+- **Brainstorming finds out why you want the thing before proposing features,** reflects your intent back for correction, and ties your approval to the actual design and planning stages. The motivating session took "that scope is ok" as permission to scaffold. (#2258)
|
|
|
+
|
|
|
+### Code Review
|
|
|
+
|
|
|
+- **Reviewers treat the spec as a vision document.** Behavior the spec is silent on is graded by what a reasonable person using the software would expect, so a crash on an unnamed input no longer slides through as Minor. A "Declined to judge" list makes every scoping decision visible, and the executor rules on each line. (#2319)
|
|
|
+- The multi-commit `BASE_SHA` alternative is now `git merge-base origin/main HEAD`. A bare `origin/main` showed main's newer files as phantom deletions once main moved past the branch point. (#2133, #2118)
|
|
|
+
|
|
|
+### Test-Driven Development
|
|
|
+
|
|
|
+- **The project's suite defines green, not just your test file.** When a task named one test file, sessions ran anything beyond it in 1 of 12 probe runs and never saw a broken neighbor. The skill now says to run the project's test command and report every failure by name, including ones you didn't cause. (#2110)
|
|
|
+
|
|
|
+### Subagent-Driven Development
|
|
|
+
|
|
|
+- **Plans with the same basename no longer share a workspace.** `docs/alpha/plan.md` and `docs/beta/plan.md` resolved to one directory and `task-brief` silently overwrote the other plan's brief. Each workspace now records its owning plan; a collision gets its own directory. Existing workspaces are adopted in place. (#2138, #2045)
|
|
|
+- **`review-package` rejects empty or non-descendant `BASE..HEAD` ranges** (exit 3), so an implementer that committed to the wrong branch can't produce a "clean" review of nothing. (#2136, #2050)
|
|
|
+
|
|
|
+### Harness Support
|
|
|
+
|
|
|
+- **OpenCode 2.0.4+** is supported alongside V1. Skills register through V2's native API, and the bootstrap survives continuation, restart, forks, and compaction. Delegated child sessions no longer receive the controller's bootstrap. (#2106, #2306)
|
|
|
+- **Muse**: native plugin manifest and SessionStart hook. `muse plugins install ./` then `muse plugins approve superpowers`. (#2317)
|
|
|
+- **Qwen Code** added to the install docs: `qwen extensions install obra/superpowers`. (#2132)
|
|
|
+- **Claude Code** gets a platform reference describing an opt-in nested orchestrator: running the subagent-driven controller one layer down on a mid-tier model measured about half the cost and wall clock. (#2320)
|
|
|
+
|
|
|
+### Fixes
|
|
|
+
|
|
|
+- **Skills work when a packager strips executable bits.** The Codex marketplace and MiniMax Code's repackage both shipped our scripts non-executable, so every documented command failed with `Permission denied`. Skill prose now invokes bundled scripts through their interpreter (`bash scripts/foo.sh`, `node render-graphs.js`), and the SDD helpers call each other the same way. (#2301, #2134, #2040)
|
|
|
+- The platform-support issue template applies a label that exists (`new-harness`). (#2250)
|
|
|
+
|
|
|
+### Documentation
|
|
|
+
|
|
|
+- `docs/testing.md` describes the Quorum eval lab, replacing stale Drill references and commands. (#2135)
|
|
|
+- README: a "When Something Goes Wrong" section pointing at `diagnosing-superpowers`.
|
|
|
+- `AGENTS.md` is now the regular file and `CLAUDE.md` points at it; Muse's installer rejects symlinks.
|
|
|
+- Adopted the Prime Radiant Community Code of Conduct. (#2122)
|
|
|
+
|
|
|
## v6.3.0 (2026-08-12)
|
|
|
|
|
|
### Harness Support
|
Jesse Vincent