forked from bchanot/claude
chore(config): superpowers citers by bare name, routing map, docs, settings
Every superpowers-prefixed skill call in ship-feature, init-project, tour, deploy, audit-delta, plugin-advisor and lib/analyze-before-plan now names the vendored skill directly. finishing-a-development-branch is described as the upstream skill this config does not vendor (gitflow finish is the integration path). CLAUDE.global.md Skill routing maps the four non-vendored skills the vendored text still references. settings.json loses the plugin key and its marketplace block; README, USAGE, plugin-advisor and the profile skill describe superpowers as vendored skills, always on, zero plugin cost. CHANGELOG entry with a known residual.
This commit is contained in:
bastien
@@ -318,7 +318,8 @@ Then offer to capitalize (per CLAUDE.md): recurring finding patterns →
|
||||
|
||||
## TDD note (skill itself)
|
||||
|
||||
Baseline-tested per superpowers:writing-skills (2026-06-11, isolated
|
||||
Baseline-tested per writing-skills (vendored superpowers skill;
|
||||
2026-06-11, isolated
|
||||
worktree, no skill): the agent (1) guessed the boundary from the most
|
||||
recent file date in `.claude/audits/` — wrong file, date-based; (2) wrote
|
||||
its checkpoint as prose in a dated report — unparseable next run; (3) kept
|
||||
|
||||
@@ -512,7 +512,7 @@ The deploy succeeded. Lay the oracle and close out.
|
||||
|
||||
## Note on this skill (authoring)
|
||||
|
||||
Shaped via `superpowers:writing-skills`. The **cold cross-session resume** is the
|
||||
Shaped via `writing-skills` (vendored superpowers skill). The **cold cross-session resume** is the
|
||||
novel form (design §10): the disk alone must carry the deploy across the
|
||||
out-of-band gap, so `PENDING.json`'s presence marks the wait and STEP 0 resumes
|
||||
from it without conversation memory — the `audit-delta` "state file is the only
|
||||
|
||||
@@ -13,8 +13,10 @@ fan-out, init, `.gitignore` reconcile, the protected-base predicate — are in
|
||||
and bulletproofs the single judgment call: **`finish` merges only on an explicit
|
||||
human signal.**
|
||||
|
||||
Replaces `finishing-a-development-branch` for gitflow flows — that skill is
|
||||
single-target and cannot do the directed / fan-out merges below.
|
||||
Replaces `finishing-a-development-branch` (upstream superpowers skill, not
|
||||
vendored here; `gitflow finish` is the only integration path) for gitflow
|
||||
flows — that skill is single-target and cannot do the directed / fan-out
|
||||
merges below.
|
||||
|
||||
## When to Use
|
||||
|
||||
@@ -107,7 +109,7 @@ stays human-gated.
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Using `finishing-a-development-branch` for a gitflow merge → it can't do directed/fan-out merges. Use `gitflow finish`.
|
||||
- Using `finishing-a-development-branch` (upstream superpowers skill, not vendored here) for a gitflow merge → it can't do directed/fan-out merges anyway. Use `gitflow finish`, the only integration path.
|
||||
- Hand-writing `git merge` instead of `gitflow finish` → loses fan-out, branch delete, base sync.
|
||||
- Calling `finish` because the work *looks* done → see the gate.
|
||||
- `git branch -d`/`-D` by hand → denied; a branch the lib refuses to delete still holds work. Keep it, say so.
|
||||
|
||||
@@ -68,7 +68,7 @@ contract.
|
||||
Load `$HOME/.claude/agents/analyzer.md`. Analyze BRIEF: existing code, stack constraints, infra risks, open decisions. Produce ANALYSIS REPORT.
|
||||
|
||||
## STEP 3 — DESIGN
|
||||
Invoke `superpowers:brainstorming` with BRIEF + ANALYSIS REPORT.
|
||||
Invoke `brainstorming` (vendored superpowers skill) with BRIEF + ANALYSIS REPORT.
|
||||
Produce DESIGN: stack+versions, full folder tree, module responsibilities, data flow, interfaces (signatures only), config+tooling, test strategy, resolved decisions, prereqs list.
|
||||
Then run pass B of `$HOME/.claude/lib/contract-interview.md` against the DESIGN
|
||||
(minus what the BRIEF and the brainstorm settled): one batch before STEP 4;
|
||||
@@ -179,7 +179,7 @@ This is the deterministic scaffold commit owner (closes BLK-010). The MVP is
|
||||
implemented on a `feature/*` branch off `develop` (STEP 8).
|
||||
|
||||
## STEP 6 — PLAN
|
||||
Invoke `superpowers:writing-plans` with BRIEF + skeleton.
|
||||
Invoke `writing-plans` (vendored superpowers skill) with BRIEF + skeleton.
|
||||
Granular tasks (2-5 min each), exact file paths, TDD: tests before code.
|
||||
|
||||
## STEP 6b — CHALLENGE THE PLAN (before the gate)
|
||||
@@ -212,7 +212,7 @@ Start the MVP feature branch off develop, then implement on it:
|
||||
```bash
|
||||
bash "$HOME/.claude/lib/gitflow.sh" start feature mvp
|
||||
```
|
||||
Invoke `superpowers:subagent-driven-development` for the per-task implement loop
|
||||
Invoke `subagent-driven-development` (vendored superpowers skill) for the per-task implement loop
|
||||
**and** the final whole-branch review **only**. Do NOT run its terminal
|
||||
`finishing-a-development-branch` step — this orchestrator owns integration via
|
||||
`gitflow finish` (STEP 11). When SDD's flow reaches "Use
|
||||
@@ -256,7 +256,7 @@ against the founding contract. Distinct axis from STEP 10 code review
|
||||
([[LRN-095]]) — both run.
|
||||
|
||||
## STEP 10 — CODE REVIEW
|
||||
Invoke `superpowers:requesting-code-review`. **Model routing (BDR-077):** the
|
||||
Invoke `requesting-code-review` (vendored superpowers skill). **Model routing (BDR-077):** the
|
||||
review subagent it dispatches MUST carry `model: "opus"` in the Agent call —
|
||||
craft review is dispatched judgment, never inherited from the session. Fix
|
||||
all CRITICAL before proceeding.
|
||||
|
||||
@@ -56,8 +56,10 @@ lists items + types:
|
||||
| `mcp` | advisory — prints manual `claude mcp add …` command (no server is managed today: `MANAGED_MCPS` is empty since 21st.dev moved to a CLI) |
|
||||
| `cli` | advisory only — reports installed/not-installed |
|
||||
|
||||
**Always-on plugins** (`security-guidance`, `superpowers`) are
|
||||
protected — `set` will refuse to disable them even if the profile omits them.
|
||||
**Always-on plugins** (`security-guidance`) and the vendored superpowers
|
||||
skills are never toggled by a profile — `set` will refuse to disable the
|
||||
plugin even if the profile omits it, and the 7 superpowers skills are
|
||||
linked outside any profile.
|
||||
**Managed plugins** that `set` may disable when not in profile:
|
||||
`ui-ux-pro-max@ui-ux-pro-max-skill`, `plugin-dev@claude-code-plugins`,
|
||||
`pr-review-toolkit@claude-code-plugins`. Other plugins are never auto-toggled.
|
||||
|
||||
@@ -100,7 +100,7 @@ approved at STEP 3 ENRICHES it, and STEP 5's verifier judges the diff against
|
||||
the ENRICHED contract. This is the only flow where the contract grows mid-run.
|
||||
|
||||
## STEP 1 — BRAINSTORM
|
||||
Invoke `superpowers:brainstorming` — but FEED it the STEP 0d digest as binding context,
|
||||
Invoke `brainstorming` (vendored superpowers skill) — but FEED it the STEP 0d digest as binding context,
|
||||
not the raw request alone:
|
||||
"Feature request: <$ARGUMENTS>.
|
||||
In-force constraints (must hold): <only the IN-FORCE + ALREADY-SEEN items from 0d's
|
||||
@@ -114,7 +114,7 @@ Consumption = INPUT INJECTION (we can't modify the external skill; we control it
|
||||
Refine request into validated design via Socratic questioning. Don't proceed until design approved.
|
||||
|
||||
## STEP 2 — PLAN
|
||||
Invoke `superpowers:writing-plans` with the validated design AND the 0d digest: every task
|
||||
Invoke `writing-plans` (vendored superpowers skill) with the validated design AND the 0d digest: every task
|
||||
must be consistent with the in-force constraints; where a task implements or affects one,
|
||||
note the ID inline. Break design into tasks (2-5 min each). Each task: exact file paths, full code, verification steps.
|
||||
Then run pass B of `$HOME/.claude/lib/contract-interview.md` against the plan:
|
||||
@@ -173,7 +173,7 @@ Start the feature branch off develop, then implement on it:
|
||||
```bash
|
||||
bash "$HOME/.claude/lib/gitflow.sh" start feature <name>
|
||||
```
|
||||
Invoke `superpowers:subagent-driven-development` for the per-task implement loop
|
||||
Invoke `subagent-driven-development` (vendored superpowers skill) for the per-task implement loop
|
||||
**and** the final whole-branch review **only**. Do NOT run its terminal
|
||||
`finishing-a-development-branch` step — this orchestrator owns integration via
|
||||
`gitflow finish` (STEP 9). When SDD's flow reaches "Use
|
||||
@@ -234,7 +234,7 @@ conformity + security vs. craft/design) — both run, neither subsumes the
|
||||
other ([[LRN-095]]).
|
||||
|
||||
## STEP 6 — CODE REVIEW
|
||||
Invoke `superpowers:requesting-code-review`. **Model routing (BDR-077):** the
|
||||
Invoke `requesting-code-review` (vendored superpowers skill). **Model routing (BDR-077):** the
|
||||
review subagent it dispatches MUST carry `model: "opus"` in the Agent call —
|
||||
craft review is dispatched judgment, never inherited from the session. Fix
|
||||
all CRITICAL before proceeding.
|
||||
|
||||
@@ -315,9 +315,10 @@ without that approval — neither this repo's nor any target project's.
|
||||
|
||||
## TDD note (skill itself)
|
||||
|
||||
Baseline-tested per superpowers:writing-skills (2026-07-04, seeded
|
||||
fixture, no skill): the agent branched correctly via gitflow and did not
|
||||
merge, BUT (1) silently rewrote the target TODO (checked boxes,
|
||||
Baseline-tested per writing-skills (vendored superpowers skill;
|
||||
2026-07-04, seeded fixture, no skill): the agent branched correctly via
|
||||
gitflow and did not merge, BUT (1) silently rewrote the target TODO (checked
|
||||
boxes,
|
||||
restructured) during "reconcile"; (2) authored BDR/journal registry
|
||||
entries autonomously; (3) ran security as ad-hoc grep + ruff — no
|
||||
semgrep, no pinned rulesets; (4) left findings only in its final chat
|
||||
|
||||
Reference in New Issue
Block a user