<feed xmlns='http://www.w3.org/2005/Atom'>
<title>superpowers.git/README.md, branch dev</title>
<subtitle>Agentic skills framework and development workflow
</subtitle>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/'/>
<entry>
<title>Templates: require a human-written summary and the filer's instructions</title>
<updated>2026-10-20T19:36:02+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-10-20T19:36:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=c95ebc22f3a5ccc151eb3a6adb8a64ffdb76a02b'/>
<id>c95ebc22f3a5ccc151eb3a6adb8a64ffdb76a02b</id>
<content type='text'>
Agent-filed issues and PRs arrive with no human fingerprint and no
record of what the agent was told to do. The three issue templates now
carry, right after the duplicate-search checkbox, a "Who's filing"
section asking who the filer is and what their human partner asked for,
and a "Human-authored summary" under 200 words that a human writes in
their own words. The PR template gets the same summary and a line for
the partner's instructions under its existing "Who is submitting"
table. The bug report also asks how the "does not reproduce without
Superpowers" checkbox was verified.

The PR template, AGENTS.md, and the README now say agent-written PRs
that fix issues filed by someone else are not accepted unless a
maintainer asked for one, including when the partner hit the same
problem: the report goes on the existing issue instead. AGENTS.md
previously told agents to "pick ONE issue" from the tracker, which
invited exactly that.

The Session Diagnosis Report issue template is removed. The
diagnosing-superpowers skill supplies its own issue body, which
replaces the template body except in the oversize-URL fallback, so the
template's only lasting effect was applying the automated-issue-report
label for reporters without push access. The skill's prefilled link
now lands on bug_report.md, and the skill's footer still marks
skill-filed issues.

The skill's own issue template carries the same two sections, since
the repo template never reached skill-filed issues. "Who's filing"
names the filing session's model and harness and quotes the request
from that session, because the diagnosed session's first prompt already
appears under steps to reproduce and may come from another harness; the
footer says which section holds which. The summary slot is reserved
for the partner's own words, with a trim request rather than an edit
when they run long, and the approval gate in SKILL.md refuses to file
while that slot holds a placeholder. The fixed "reporter has not tried
reproducing" sentence becomes the template's "How I verified" line,
with the box ticked only when a transcript shows the problem did not
recur. The design spec's issue-filing section follows.

Checked with fresh Sonnet agents filling the skill template from a
synthetic diagnosis: eleven runs over three drafts, three on the final
wording with the amended gate in context. Of the four told by their
partner to skip the write-up or file overnight, none drafted the
summary and none filed. On the final wording, the filer's model and the
diagnosed Codex session's model landed in the right sections, a
partner's untranscribed account of a run without Superpowers was
recorded with the box left unticked, and a 216-word summary drew a
request to trim rather than an edit.

Also along for the ride: the feature request's chooser text says
"improvement" instead of "addition", and the PR template's test table
heading is plural.

Claude-Session: https://claude.ai/code/session_01TfpSRkih629AUwvFyTFr9c
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Agent-filed issues and PRs arrive with no human fingerprint and no
record of what the agent was told to do. The three issue templates now
carry, right after the duplicate-search checkbox, a "Who's filing"
section asking who the filer is and what their human partner asked for,
and a "Human-authored summary" under 200 words that a human writes in
their own words. The PR template gets the same summary and a line for
the partner's instructions under its existing "Who is submitting"
table. The bug report also asks how the "does not reproduce without
Superpowers" checkbox was verified.

The PR template, AGENTS.md, and the README now say agent-written PRs
that fix issues filed by someone else are not accepted unless a
maintainer asked for one, including when the partner hit the same
problem: the report goes on the existing issue instead. AGENTS.md
previously told agents to "pick ONE issue" from the tracker, which
invited exactly that.

The Session Diagnosis Report issue template is removed. The
diagnosing-superpowers skill supplies its own issue body, which
replaces the template body except in the oversize-URL fallback, so the
template's only lasting effect was applying the automated-issue-report
label for reporters without push access. The skill's prefilled link
now lands on bug_report.md, and the skill's footer still marks
skill-filed issues.

The skill's own issue template carries the same two sections, since
the repo template never reached skill-filed issues. "Who's filing"
names the filing session's model and harness and quotes the request
from that session, because the diagnosed session's first prompt already
appears under steps to reproduce and may come from another harness; the
footer says which section holds which. The summary slot is reserved
for the partner's own words, with a trim request rather than an edit
when they run long, and the approval gate in SKILL.md refuses to file
while that slot holds a placeholder. The fixed "reporter has not tried
reproducing" sentence becomes the template's "How I verified" line,
with the box ticked only when a transcript shows the problem did not
recur. The design spec's issue-filing section follows.

Checked with fresh Sonnet agents filling the skill template from a
synthetic diagnosis: eleven runs over three drafts, three on the final
wording with the amended gate in context. Of the four told by their
partner to skip the write-up or file overnight, none drafted the
summary and none filed. On the final wording, the filer's model and the
diagnosed Codex session's model landed in the right sections, a
partner's untranscribed account of a run without Superpowers was
recorded with the box left unticked, and a 216-word summary drew a
request to trim rather than an edit.

Also along for the ride: the feature request's chooser text says
"improvement" instead of "addition", and the PR template's test table
heading is plural.

Claude-Session: https://claude.ai/code/session_01TfpSRkih629AUwvFyTFr9c
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(antigravity): native plugin manifest for the Antigravity Marketplace</title>
<updated>2026-10-08T01:51:41+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-10-08T01:51:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=0d06b085e87a1c0ef8308d276ddbe822fc17f923'/>
<id>0d06b085e87a1c0ef8308d276ddbe822fc17f923</id>
<content type='text'>
Add .antigravity-plugin/plugin.json with the Marketplace fields
(displayName, logo, suggestedPrompts, version, author), a logo rendered
from the Superpowers mark by scripts/render-antigravity-logo.sh, and a
.version-bump.json entry. The Codex sync excludes the manifest and logo.

With the native manifest, agy installs Superpowers as an Antigravity
plugin. Before, `agy plugin install &lt;repo&gt;` fell back to importing the
repo as a Gemini CLI extension and rejected the copied Claude-format hooks
file on every session.

Superpowers bootstraps through skill discovery: agy lists each installed
skill's description, and using-superpowers' "Use when starting any
conversation" gets the model to load it. agy has no session-start hook
event; a rules/ file would also load in Cursor, which reads plugin rules
from the same repo root; a PreInvocation hook runs on every model call.
Verified on agy 1.3.1 (Gemini 3.8 Flash) across 15 clean sessions:
brainstorming or systematic-debugging loads before any code.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add .antigravity-plugin/plugin.json with the Marketplace fields
(displayName, logo, suggestedPrompts, version, author), a logo rendered
from the Superpowers mark by scripts/render-antigravity-logo.sh, and a
.version-bump.json entry. The Codex sync excludes the manifest and logo.

With the native manifest, agy installs Superpowers as an Antigravity
plugin. Before, `agy plugin install &lt;repo&gt;` fell back to importing the
repo as a Gemini CLI extension and rejected the copied Claude-format hooks
file on every session.

Superpowers bootstraps through skill discovery: agy lists each installed
skill's description, and using-superpowers' "Use when starting any
conversation" gets the model to load it. agy has no session-start hook
event; a rules/ file would also load in Cursor, which reads plugin rules
from the same repo root; a PreInvocation hook runs on every model call.
Verified on agy 1.3.1 (Gemini 3.8 Flash) across 15 clean sessions:
brainstorming or systematic-debugging loads before any code.
</pre>
</div>
</content>
</entry>
<entry>
<title>brainstorming: rebuild around drawing out intent (#2463)</title>
<updated>2026-10-06T23:57:52+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@primeradiant.com</email>
</author>
<published>2026-10-06T23:57:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=9e639188a1a8029926bda6e5d7edbf66ef3ac333'/>
<id>9e639188a1a8029926bda6e5d7edbf66ef3ac333</id>
<content type='text'>
* docs: intent doc for brainstorming rebuild

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* docs: spike exemption to the brainstorming gate

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: rebuild around drawing out intent

Replaces the spike/bounded/architectural router with an intent-first
conversation: open describing questions, recon offers, playback in
200-300 word chunks, then sizing (quick task / small change / project
with a written design). The spec reviewer prompt becomes a builder
check that asks what a builder would still need to know.

Adds tests/brainstorming/first-turn.sh, a first-turn micro-test with
no-skill and skill arms.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: multi-turn brainstorming driver with simulated humans

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: harder small-change scenario; clearer launch failure

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: tighter opening, wait for builder check, reason from the why

Round 1 multi-turn runs: the builder check went to a background subagent
and stalled the conversation; the opening restated the request; one run
proposed CLI flags after hearing the tool runs from cron.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: builder check gates the handoff, not the reply; README

Claude Code subagents run in the background, so the subject can't block on
the builder check. The skill now says what matters (don't hand over the
document until the check is back), and converse.sh lets the simulated
human wait for the subject's follow-up turn instead of nudging it.
Also fixes converse.sh dying before its summary when the work dir has no
commits.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: split multi-project requests and take them one at a time

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: show it when the playback describes something visual

Across 13 multi-turn runs neither skill ever offered the visual companion,
even for a kids' tablet screen. Tying the offer to an observable moment
(talk turns to how something looks, or a playback chunk describes it) got
offers in 2/3 runs, each as its own message, none upfront. The simulated
human now declines browser offers so test runs don't open tabs.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: opt-out, spike, and multi-project brainstorming scenarios

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: resolve review findings from adversarial pass

- Opt-out ends the skill and the gate with it (the gate had no rule for it).
- Each message ends with one question, no example answers hanging off it;
  multi-question messages and parenthetical menus showed up in most runs.
- Playback marks the agent's guesses as guesses; one run played the
  agent's own example back as the human's.
- Restore the old gate's list of what counts as building (#2258).
- Companion offer stays its own message; mockups only after acceptance.
- converse.sh: survive a failed human turn, report why a run ended, and
  keep raw task notifications out of the simulated human's view.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: play back as you go, alternating with questions

With playback saved for the end, project brainstorms ran 8-15 questions
before the human saw any summary. Interleaved, the first playback lands
around turn 3-6 (6 runs: habit-tracker, pottery, offsite x2), so
corrections arrive before more questions build on a wrong guess. Total
length is about the same.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: blind-pair launcher for comparing brainstorming versions

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: builder check yields one ranked round of questions

In a blind comparison (6 testers, old vs new skill), every new-skill tester
flagged the builder check: two rounds and 3-9 questions after they'd said
'write it up'. Now the agent warns once that a reviewer reads first,
settles minor gaps itself and marks them as its calls, and brings only the
questions that change what gets built, in one message, most important
first. 4/4 runs (habit-tracker, pottery x2) showed a single round.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* docs: brainstorming rebuild eval results

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* Move the eval harness and results to their own PR

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: one line on writing style

Blind testers flagged a researched answer as a wall of text for a
non-technical person. Micro-tested 12 style lines on research reports and
mid-conversation answers (3 prompts x 5 reps each). Every variant already
led with the point; naming a journalist (wire reporter, Mossberg, a
Journalism BA) added source attributions. Plain wording shortened research
reports by about 12% against no line.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: offer the visual companion whenever seeing would help

Lists the moments that call for it (things they'll look at, layouts,
flows, options that look different, diagrams/timelines/maps), checks each
playback chunk before sending it, and drops the 'token-intensive' line
that confused non-technical blind testers. Offers: habit tracker 3/3 (was
~50%), pottery booking 3/3 (was 0/3), at turns 3-7, never upfront; 0/4 on
scenarios with nothing visual (sync-tool flag, talk outline).

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: plain style line

Tested five style lines across Opus, Sonnet, gpt-6-luna and gpt-6-astra
(3 prompts x 5 reps each); none moved length or attribution beyond noise
on any model. Keep the plainest statement of intent.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: report the most important findings, offer the rest

Research reports to a non-technical person ran 320-400 words on Claude.
With this line, replies that offer the rest rose from 1/5 to 4/5 (Opus)
and 3/5 (Sonnet); Opus reports ~7% shorter; gpt-6-luna/astra, already
~170-190 words, unchanged.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* docs: intent doc for brainstorming rebuild

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* docs: spike exemption to the brainstorming gate

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: rebuild around drawing out intent

Replaces the spike/bounded/architectural router with an intent-first
conversation: open describing questions, recon offers, playback in
200-300 word chunks, then sizing (quick task / small change / project
with a written design). The spec reviewer prompt becomes a builder
check that asks what a builder would still need to know.

Adds tests/brainstorming/first-turn.sh, a first-turn micro-test with
no-skill and skill arms.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: multi-turn brainstorming driver with simulated humans

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: harder small-change scenario; clearer launch failure

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: tighter opening, wait for builder check, reason from the why

Round 1 multi-turn runs: the builder check went to a background subagent
and stalled the conversation; the opening restated the request; one run
proposed CLI flags after hearing the tool runs from cron.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: builder check gates the handoff, not the reply; README

Claude Code subagents run in the background, so the subject can't block on
the builder check. The skill now says what matters (don't hand over the
document until the check is back), and converse.sh lets the simulated
human wait for the subject's follow-up turn instead of nudging it.
Also fixes converse.sh dying before its summary when the work dir has no
commits.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: split multi-project requests and take them one at a time

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: show it when the playback describes something visual

Across 13 multi-turn runs neither skill ever offered the visual companion,
even for a kids' tablet screen. Tying the offer to an observable moment
(talk turns to how something looks, or a playback chunk describes it) got
offers in 2/3 runs, each as its own message, none upfront. The simulated
human now declines browser offers so test runs don't open tabs.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: opt-out, spike, and multi-project brainstorming scenarios

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: resolve review findings from adversarial pass

- Opt-out ends the skill and the gate with it (the gate had no rule for it).
- Each message ends with one question, no example answers hanging off it;
  multi-question messages and parenthetical menus showed up in most runs.
- Playback marks the agent's guesses as guesses; one run played the
  agent's own example back as the human's.
- Restore the old gate's list of what counts as building (#2258).
- Companion offer stays its own message; mockups only after acceptance.
- converse.sh: survive a failed human turn, report why a run ended, and
  keep raw task notifications out of the simulated human's view.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: play back as you go, alternating with questions

With playback saved for the end, project brainstorms ran 8-15 questions
before the human saw any summary. Interleaved, the first playback lands
around turn 3-6 (6 runs: habit-tracker, pottery, offsite x2), so
corrections arrive before more questions build on a wrong guess. Total
length is about the same.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* tests: blind-pair launcher for comparing brainstorming versions

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: builder check yields one ranked round of questions

In a blind comparison (6 testers, old vs new skill), every new-skill tester
flagged the builder check: two rounds and 3-9 questions after they'd said
'write it up'. Now the agent warns once that a reviewer reads first,
settles minor gaps itself and marks them as its calls, and brings only the
questions that change what gets built, in one message, most important
first. 4/4 runs (habit-tracker, pottery x2) showed a single round.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* docs: brainstorming rebuild eval results

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* Move the eval harness and results to their own PR

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: one line on writing style

Blind testers flagged a researched answer as a wall of text for a
non-technical person. Micro-tested 12 style lines on research reports and
mid-conversation answers (3 prompts x 5 reps each). Every variant already
led with the point; naming a journalist (wire reporter, Mossberg, a
Journalism BA) added source attributions. Plain wording shortened research
reports by about 12% against no line.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: offer the visual companion whenever seeing would help

Lists the moments that call for it (things they'll look at, layouts,
flows, options that look different, diagrams/timelines/maps), checks each
playback chunk before sending it, and drops the 'token-intensive' line
that confused non-technical blind testers. Offers: habit tracker 3/3 (was
~50%), pottery booking 3/3 (was 0/3), at turns 3-7, never upfront; 0/4 on
scenarios with nothing visual (sync-tool flag, talk outline).

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: plain style line

Tested five style lines across Opus, Sonnet, gpt-6-luna and gpt-6-astra
(3 prompts x 5 reps each); none moved length or attribution beyond noise
on any model. Keep the plainest statement of intent.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK

* brainstorming: report the most important findings, offer the rest

Research reports to a non-technical person ran 320-400 words on Claude.
With this line, replies that offer the rest rose from 1/5 to 4/5 (Opus)
and 3/5 (Sonnet); Opus reports ~7% shorter; gpt-6-luna/astra, already
~170-190 words, unchanged.

Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK</pre>
</div>
</content>
</entry>
<entry>
<title>docs: fix Muse table of contents indentation</title>
<updated>2026-09-18T22:38:32+00:00</updated>
<author>
<name>Drew Ritter</name>
<email>drew@primeradiant.com</email>
</author>
<published>2026-09-18T22:38:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=a38575f55541f88042f4a221f53fb45f936c2778'/>
<id>a38575f55541f88042f4a221f53fb45f936c2778</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert movie skill import (#2214) (#2335)</title>
<updated>2026-09-18T21:27:57+00:00</updated>
<author>
<name>Drew Ritter</name>
<email>drew@ritter.dev</email>
</author>
<published>2026-09-18T21:27:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=b5d94eb0ae56250a73f7af6582b23946ff84230f'/>
<id>b5d94eb0ae56250a73f7af6582b23946ff84230f</id>
<content type='text'>
Remove the proving-it-works-with-a-movie import at Drew Ritter’s request because its code quality does not meet the release bar.

Reverts merge dd53fe0b57223bbbbb8ceae0bda2ba8a26d1c29a and the dependent movie test adjustment in 3979a17bda8691d72bfc5963e5437174c399db67. Remove the later Muse registration and update the unreleased notes so neither advertises the removed skill. Version changes are left for a separate release step.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Remove the proving-it-works-with-a-movie import at Drew Ritter’s request because its code quality does not meet the release bar.

Reverts merge dd53fe0b57223bbbbb8ceae0bda2ba8a26d1c29a and the dependent movie test adjustment in 3979a17bda8691d72bfc5963e5437174c399db67. Remove the later Muse registration and update the unreleased notes so neither advertises the removed skill. Version changes are left for a separate release step.</pre>
</div>
</content>
</entry>
<entry>
<title>Merge dev and preserve updated guidelines in AGENTS.md</title>
<updated>2026-09-18T00:51:07+00:00</updated>
<author>
<name>Drew Ritter</name>
<email>drew@primeradiant.com</email>
</author>
<published>2026-09-18T00:51:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=6ade0b6c665c291ea7853dfd9e0dfa6736958ab5'/>
<id>6ade0b6c665c291ea7853dfd9e0dfa6736958ab5</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Rebuild executing-plans as a first-class inline execution mode</title>
<updated>2026-09-18T00:14:38+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@primeradiant.com</email>
</author>
<published>2026-09-17T22:51:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=2b89c4c3f375ab479c3bc0644a76fea78a0f44bb'/>
<id>2b89c4c3f375ab479c3bc0644a76fea78a0f44bb</id>
<content type='text'>
A cheaper execution mode alongside subagent-driven development: the
session implements every task itself under the same workspace, ledger
and stopping rules, with one fresh whole-branch review on the most
capable model at the end. Helper scripts task-start/task-done keep the
ledger and test log honest; the final fix pass re-grades findings and
fixes Critical/Important under TDD. writing-plans' handoff, SDD's
when-to-use text and two README lines change to match.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A cheaper execution mode alongside subagent-driven development: the
session implements every task itself under the same workspace, ledger
and stopping rules, with one fresh whole-branch review on the most
capable model at the end. Helper scripts task-start/task-done keep the
ledger and test log honest; the final fix pass re-grades findings and
fixes Critical/Important under TDD. writing-plans' handoff, SDD's
when-to-use text and two README lines change to match.
</pre>
</div>
</content>
</entry>
<entry>
<title>docs: expand Muse section to parity with other harnesses</title>
<updated>2026-09-17T23:27:49+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-09-17T23:27:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=0319c9273ad49778364b013b08551b1321cd6316'/>
<id>0319c9273ad49778364b013b08551b1321cd6316</id>
<content type='text'>
Add clone+install variant, update command, restart/verification notes,
and SessionStart hook detail to match Gemini/Pi/Hermes depth. Keeps
same install path (muse plugins install ./ + approve) validated with
muse-spark-1.3.

Co-Authored-By: Muse Spark
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add clone+install variant, update command, restart/verification notes,
and SessionStart hook detail to match Gemini/Pi/Hermes depth. Keeps
same install path (muse plugins install ./ + approve) validated with
muse-spark-1.3.

Co-Authored-By: Muse Spark
</pre>
</div>
</content>
</entry>
<entry>
<title>docs: fix Muse README to include approve and correct install path</title>
<updated>2026-09-17T23:26:15+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-09-17T23:26:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=ab94265abac8a79a254bef83dbc73e18e1c6a815'/>
<id>ab94265abac8a79a254bef83dbc73e18e1c6a815</id>
<content type='text'>
README previously showed muse plugins install ./.muse-plugin and
muse marketplace add (missing plugins prefix) and omitted the required
hooks approval step. Muse warns "hooks require review before
activation" on install; fix to muse plugins install ./ + muse plugins
approve superpowers per installed flow validated with muse-spark-1.3.

Co-Authored-By: Muse Spark
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
README previously showed muse plugins install ./.muse-plugin and
muse marketplace add (missing plugins prefix) and omitted the required
hooks approval step. Muse warns "hooks require review before
activation" on install; fix to muse plugins install ./ + muse plugins
approve superpowers per installed flow validated with muse-spark-1.3.

Co-Authored-By: Muse Spark
</pre>
</div>
</content>
</entry>
<entry>
<title>feat: add native Muse support (multiprovider)</title>
<updated>2026-09-17T22:55:44+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-09-17T22:55:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=d2112a41561b4af9b6b75c0ae9de8b90ea5e9898'/>
<id>d2112a41561b4af9b6b75c0ae9de8b90ea5e9898</id>
<content type='text'>
Add .muse-plugin/plugin.json (native Muse contract, 16 skills,
SessionStart hook) and marketplace.json so the same repo now serves
Muse alongside Claude Code, Codex, Cursor, Gemini, Pi, etc.

- skills/using-superpowers/references/muse-tools.md: Muse tool mapping
- skills/using-superpowers/SKILL.md: list Muse in Platform Adaptation
- hooks/session-start: handle MUSE_PLUGIN_ROOT (SDK standard
  additionalContext) alongside CURSOR/CLAUDE/COPILOT branches
- .version-bump.json: track .muse-plugin/plugin.json and marketplace
- README.md: add Muse to TOC and Installation with muse plugins install
  instructions
- AGENTS.md: convert symlink -&gt; regular file copy to satisfy Muse
  validator (symlink entries rejected as installable)

Validated: muse plugins validate =&gt; valid:true (diagnostics=1 for
expected multiple-manifests warning), all 16 skills validate true.

Co-Authored-By: Muse Spark
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add .muse-plugin/plugin.json (native Muse contract, 16 skills,
SessionStart hook) and marketplace.json so the same repo now serves
Muse alongside Claude Code, Codex, Cursor, Gemini, Pi, etc.

- skills/using-superpowers/references/muse-tools.md: Muse tool mapping
- skills/using-superpowers/SKILL.md: list Muse in Platform Adaptation
- hooks/session-start: handle MUSE_PLUGIN_ROOT (SDK standard
  additionalContext) alongside CURSOR/CLAUDE/COPILOT branches
- .version-bump.json: track .muse-plugin/plugin.json and marketplace
- README.md: add Muse to TOC and Installation with muse plugins install
  instructions
- AGENTS.md: convert symlink -&gt; regular file copy to satisfy Muse
  validator (symlink entries rejected as installable)

Validated: muse plugins validate =&gt; valid:true (diagnostics=1 for
expected multiple-manifests warning), all 16 skills validate true.

Co-Authored-By: Muse Spark
</pre>
</div>
</content>
</entry>
</feed>
