From e7a2d16476bf042e9add4699c9d018a90f86e4a6 Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Mon, 27 Apr 2026 21:55:33 -0700 Subject: [PATCH] Require session transcript for new-harness PRs 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. --- .github/PULL_REQUEST_TEMPLATE.md | 39 ++++++++++++++++++++++++++++++++ CLAUDE.md | 21 +++++++++++++++++ 2 files changed, 60 insertions(+) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 4308271f..4867ac72 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -50,6 +50,45 @@ of human involvement will be closed without review. |-------------------------------------|-----------------|-------|------------------| | | | | | +## New harness support (required if this PR adds a new harness) + + + +
+Clean-session transcript for "Let's make a react todo list" + +``` +paste the complete transcript here +``` + +
+ ## Evaluation - What was the initial prompt you (or your human partner) used to start the session that led to this change? diff --git a/CLAUDE.md b/CLAUDE.md index 3a50e0fd..9bd3e00b 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -64,6 +64,27 @@ PRs containing invented claims, fabricated problem descriptions, or hallucinated PRs containing multiple unrelated changes will be closed. Split them into separate PRs. +## New Harness Support + +If your PR adds support for a new harness (IDE, CLI tool, agent runner), you MUST include a session transcript proving the integration works end-to-end. + +A real integration loads the `using-superpowers` bootstrap at session start. The bootstrap is what causes skills to auto-trigger at the right moments. Without it, the skills are dead weight — present on disk but never invoked. + +**The acceptance test.** Open a clean session in the new harness and send exactly this user message: + +> Let's make a react todo list + +A working integration auto-triggers the `brainstorming` skill before any code is written. Paste the complete transcript in the PR. + +**These are not real integrations and will be closed:** + +- Manually copying skill files into the harness +- Wrapping with `npx skills` or similar at-runtime shims +- Anything that requires the user to opt in to skills per-session +- Anything where `brainstorming` does not auto-trigger on the acceptance test above + +If you are not sure whether your integration loads the bootstrap at session start, it does not. + ## Skill Changes Require Evaluation Skills are not prose — they are code that shapes agent behavior. If you modify skill content: