Create Superpowers Lite fork

CLAUDE.md

@@ -1,4 +1,4 @@
-# Superpowers — Contributor Guidelines
+# Superpowers Lite — Contributor Guidelines
 
 ## If You Are an AI Agent
 
@@ -52,9 +52,9 @@ Every PR must solve a real problem that someone actually experienced. "My review
 
 Superpowers core contains general-purpose skills that benefit all users regardless of their project. Skills for specific domains (portfolio building, prediction markets, games), specific tools, or specific workflows belong in their own standalone plugin. Ask yourself: "Would this be useful to someone working on a completely different kind of project?" If not, publish it separately.
 
-### Fork-specific changes
+### Upstream Compatibility
 
-If you maintain a fork with customizations, do not open PRs to sync your fork or push fork-specific changes upstream. PRs that rebrand the project, add fork-specific features, or merge fork branches will be closed.
+This repository is a manual-only fork. Do not open PRs upstream for fork-specific changes such as manual activation, local-only planning artifacts, or phase-based review batching.
 
 ### Fabricated content
 
@@ -68,28 +68,28 @@ PRs containing multiple unrelated changes will be closed. Split them into separa
 
 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.
+Superpowers Lite integrations must not load the `using-superpowers` bootstrap at session start. The skills are intentionally manual-only and should activate only when the user explicitly names Superpowers Lite or a `superpowers-lite:*` skill.
 
 **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.
+A working Superpowers Lite integration does not auto-trigger `brainstorming`. It proceeds normally until the user explicitly requests Superpowers Lite.
 
 **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
+- Anything that injects Superpowers Lite skills without explicit user opt-in
+- Anything where `brainstorming` auto-triggers on the acceptance test above
 
-If you are not sure whether your integration loads the bootstrap at session start, it does not.
+If you are not sure whether your integration injects the bootstrap at session start, verify that it does not.
 
 ## Skill Changes Require Evaluation
 
 Skills are not prose — they are code that shapes agent behavior. If you modify skill content:
 
-- Use `superpowers:writing-skills` to develop and test changes
+- Use `superpowers-lite:writing-skills` to develop and test changes
 - Run adversarial pressure testing across multiple sessions
 - Show before/after eval results in your PR
 - Do not modify carefully-tuned content (Red Flags tables, rationalization lists, "human partner" language) without evidence the change is an improvement