<feed xmlns='http://www.w3.org/2005/Atom'>
<title>superpowers.git/.github, branch fix/codex-scripts-in-worktrees</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>diagnosing-superpowers: drop gh; file issues through a prefilled template link</title>
<updated>2026-09-11T22:20:09+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-09-08T19:30:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=3dd5b621a19e6a405196d3a3f7c069bd2ea18a76'/>
<id>3dd5b621a19e6a405196d3a3f7c069bd2ea18a76</id>
<content type='text'>
A default gh login carries the repo scope, which is write access to every
repository the user can reach. The skill now searches issues through the
unauthenticated public API and, instead of posting, hands the partner a
prefilled new-issue link. The link uses a new diagnosis_report.md issue
template so the bug and automated-issue-report labels apply regardless of
the reporter's permissions. Addresses arittr's review on #2236.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A default gh login carries the repo scope, which is write access to every
repository the user can reach. The skill now searches issues through the
unauthenticated public API and, instead of posting, hands the partner a
prefilled new-issue link. The link uses a new diagnosis_report.md issue
template so the bug and automated-issue-report labels apply regardless of
the reporter's permissions. Addresses arittr's review on #2236.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix platform-support issue template to apply a label that exists</title>
<updated>2026-09-03T17:56:32+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-09-03T17:56:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=573a66b67193f6cbc8851d283b5cce0c9cb4b8df'/>
<id>573a66b67193f6cbc8851d283b5cce0c9cb4b8df</id>
<content type='text'>
The template auto-applies `platform-support`, but the repo has no such label
(harness requests use `new-harness`). GitHub silently drops labels that don't
exist, so every platform-support request arrives unlabeled — the Amazon Q
request (#2194) is the latest example.

Claude-Session: https://claude.ai/code/session_01UiEfXTZAC5cuH4hgx24mbB
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The template auto-applies `platform-support`, but the repo has no such label
(harness requests use `new-harness`). GitHub silently drops labels that don't
exist, so every platform-support request arrives unlabeled — the Amazon Q
request (#2194) is the latest example.

Claude-Session: https://claude.ai/code/session_01UiEfXTZAC5cuH4hgx24mbB
</pre>
</div>
</content>
</entry>
<entry>
<title>Require contributors to disclose authoring environment and target dev</title>
<updated>2026-05-29T20:05:25+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@primeradiant.com</email>
</author>
<published>2026-05-29T19:30:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=6fd4507659784c351abbd2bc264c7162cfd386dc'/>
<id>6fd4507659784c351abbd2bc264c7162cfd386dc</id>
<content type='text'>
Add a mandatory self-identification disclosure (model, harness, harness
version, all installed plugins) to the PR template and all three issue
templates, and document the requirement in the contributor guidelines.
We weigh contributions differently depending on what produced them:
content reasoned from documentation is held to a different bar than work
grounded in a real session.

Also state explicitly, in both CLAUDE.md and the PR template, that all
PRs must target the dev branch rather than main.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add a mandatory self-identification disclosure (model, harness, harness
version, all installed plugins) to the PR template and all three issue
templates, and document the requirement in the contributor guidelines.
We weigh contributions differently depending on what produced them:
content reasoned from documentation is held to a different bar than work
grounded in a real session.

Also state explicitly, in both CLAUDE.md and the PR template, that all
PRs must target the dev branch rather than main.
</pre>
</div>
</content>
</entry>
<entry>
<title>Require session transcript for new-harness PRs</title>
<updated>2026-04-30T21:08:41+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@primeradiant.com</email>
</author>
<published>2026-04-28T04:55:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=e7a2d16476bf042e9add4699c9d018a90f86e4a6'/>
<id>e7a2d16476bf042e9add4699c9d018a90f86e4a6</id>
<content type='text'>
Most new-harness PRs ship integrations that copy skill files or wrap
with `npx skills` instead of loading the using-superpowers bootstrap at
session start. Those integrations look like they work but skills never
auto-trigger.

Add an acceptance test ("Let's make a react todo list" must auto-trigger
brainstorming in a clean session) and require the transcript in the PR.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Most new-harness PRs ship integrations that copy skill files or wrap
with `npx skills` instead of loading the using-superpowers bootstrap at
session start. Those integrations look like they work but skills never
auto-trigger.

Add an acceptance test ("Let's make a react todo list" must auto-trigger
brainstorming in a clean session) and require the transcript in the PR.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix Discord invite link</title>
<updated>2026-04-06T22:48:58+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-04-06T22:48:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=917e5f53b16b115b70a3a355ed5f4993b9f8b73d'/>
<id>917e5f53b16b115b70a3a355ed5f4993b9f8b73d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Update Discord invite link</title>
<updated>2026-04-06T22:46:52+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-04-06T22:46:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=a6b1a1fa0c367a7cf3d373e1bdb0dbc84d50ccde'/>
<id>a6b1a1fa0c367a7cf3d373e1bdb0dbc84d50ccde</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add issue templates and disable blank issues</title>
<updated>2026-03-19T20:26:17+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-03-19T20:26:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=8ea39819eed74fe2a0338e71789f06b30e953041'/>
<id>8ea39819eed74fe2a0338e71789f06b30e953041</id>
<content type='text'>
Four templates: bug report (with environment table and platform-vs-plugin
gate), feature request (with problem statement and core-appropriateness
question), IDE/platform support request, and a config that disables
blank issues and redirects questions to Discord.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Four templates: bug report (with environment table and platform-vs-plugin
gate), feature request (with problem statement and core-appropriateness
question), IDE/platform support request, and a config that disables
blank issues and redirects questions to Discord.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add PR template to filter low-quality submissions</title>
<updated>2026-03-19T20:04:32+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2026-03-19T20:04:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=764215331d88f61bd7436e39b134d34da566e581'/>
<id>764215331d88f61bd7436e39b134d34da566e581</id>
<content type='text'>
Requires contributors to articulate the problem they're solving,
confirm human review, document eval methodology, and check for
duplicate PRs. Informed by patterns in ~90 closed-without-merge PRs.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Requires contributors to articulate the problem they're solving,
confirm human review, document eval methodology, and check for
duplicate PRs. Informed by patterns in ~90 closed-without-merge PRs.
</pre>
</div>
</content>
</entry>
<entry>
<title>Update GitHub funding configuration</title>
<updated>2025-11-22T00:46:32+00:00</updated>
<author>
<name>Jesse Vincent</name>
<email>jesse@fsck.com</email>
</author>
<published>2025-11-22T00:46:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/superpowers.git/commit/?id=84283dfc058f61b8985e07d20eb6838a6e7388fe'/>
<id>84283dfc058f61b8985e07d20eb6838a6e7388fe</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
