Skip to content

feat: v3.0.0 refactor onto superpowers foundation#1

Open
BaronVonSario wants to merge 18 commits into
mainfrom
feat/superpowers-refactor
Open

feat: v3.0.0 refactor onto superpowers foundation#1
BaronVonSario wants to merge 18 commits into
mainfrom
feat/superpowers-refactor

Conversation

@BaronVonSario
Copy link
Copy Markdown
Collaborator

Summary

  • v2.5.2 → v3.0.0 (breaking). Plugin now requires the superpowers plugin as foundation. All generic workflow primitives (brainstorming, planning, execution, code review, git worktrees, parallel agents, skill writing) delegate to superpowers:* skills. This plugin keeps only Python/Django/FastAPI value + microservice orchestration.
  • 4 workflow commands rewritten as thin wrappers (brainstorm, plan, work, review) — each delegates to a superpowers:* skill while keeping Python-specific value (workflow_skills loading, microservice-focus invocation, quality gate in work, reviewer roster in review). New microservice-focus skill consolidates ~50 lines of Focus Gate logic previously duplicated across commands.
  • 3 commands deprecated as shims (/workflows:compound, /lfg, /slfg) — print migration messages, removed entirely in v4.0.0. 6 skills deleted (replaced by superpowers equivalents) + 1 agent deleted (learnings-researcher). Net change: 77 files, +677 / -11,647 lines. Counts: 33 → 32 agents; 26 → 21 skills; 21 → 18 active commands.
  • Vocabulary migrated to superpowers convention: artifacts are "specs" at docs/superpowers/specs/, plans at docs/superpowers/plans/. Knowledge-compounding pattern (docs/solutions/) dropped — legacy files in user repos still protected from accidental deletion. <focus_context> block in CLAUDE.md normalized to dependencies: key matching workflow commands.

See docs/superpowers/specs/2026-05-25-superpowers-refactor-design.md for the full design rationale and docs/superpowers/plans/2026-05-25-superpowers-refactor-plan.md for the implementation plan. CHANGELOG.md v3.0.0 entry has the user-facing migration steps.

Test Plan

This PR cannot be auto-tested — the plugin has no test framework. Reviewers should manually verify in a real Python project (single-service and ideally one multi-service) where this plugin + superpowers are installed:

  • Install superpowers first, then this plugin from this branch
  • /workflows:brainstorm "add request rate limiting" → loads superpowers:brainstorming, asks discovery questions, writes spec to docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md (NOT docs/brainstorms/)
  • /workflows:plan <spec-path> → loads superpowers:writing-plans, produces plan at docs/superpowers/plans/YYYY-MM-DD-<topic>.md
  • In a multi-service repo (multiple pyproject.toml at root): /workflows:brainstorm invokes the microservice-focus skill, prompts for services via AskUserQuestion, and writes per-service specs at {service}/docs/superpowers/specs/
  • /workflows:review spawns configured Python review agents + code-simplicity-reviewer + agent-native-reviewer — and does NOT spawn learnings-researcher
  • /workflows:compound, /lfg, /slfg each print their deprecation message and do nothing else
  • With superpowers uninstalled: HOME=/tmp bash scripts/check-dependencies.sh prints [REQUIRED] superpowers warning
  • Grep sweep: grep -rn "learnings-researcher\|compound-docs\|docs/solutions" --include="*.md" . returns matches only in CHANGELOG, the 3 shim files, and the docs/superpowers/ historical design/plan docs

🤖 Generated with Claude Code

BaronVonSario and others added 18 commits May 25, 2026 12:29
Spec: docs/superpowers/specs/2026-05-25-superpowers-refactor-design.md
Plan: docs/superpowers/plans/2026-05-25-superpowers-refactor-plan.md

Documents the v3.0.0 refactor: require superpowers plugin, delete
6 duplicate skills, drop /workflows:compound + /lfg + /slfg (shimmed),
rewrite 4 workflow commands as thin wrappers, extract microservice
focus logic into a dedicated skill.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Consolidates service discovery, --services parsing, multi-service
prompting, and <focus_context> block construction into a single
skill. Workflow commands invoke this once instead of duplicating
~50 lines of focus gate logic each.
Addresses two issues from Task 1 code quality review:

- Add Step 0 to focus-gate.md describing what to do when a
  <focus_context> block already exists in the conversation
  (parse services from it, skip rediscovery/prompt, refresh
  per-service context if stale, return).
- Normalize zero-result glob framing in service-discovery.md
  to match focus-gate.md (don't claim 'not a Python repo' —
  both 0 and 1 results mean single-service mode regardless
  of why).
Delegates brainstorming to superpowers:brainstorming. Loads Python
workflow_skills + microservice-focus skill, then hands off topic +
<focus_context> to the superpowers skill. Multi-service spec output
lands at {service}/docs/superpowers/specs/ (was docs/brainstorms/).

189 lines → 45 lines.
Resolves Task 2 review ambiguity. superpowers:brainstorming always
writes one spec at the default root path; the wrapper post-processes
in multi-service mode by copying to per-service paths, prepending a
## Services section, and deleting the root spec to avoid duplication.
Single-service mode unchanged (root spec is the final artifact).
Delegates plan writing to superpowers:writing-plans. Loads Python
workflow_skills + microservice-focus skill, then hands off topic +
<focus_context>. Multi-service post-processing adds services: YAML
frontmatter, writes per-service plan files at {service}/docs/
superpowers/plans/, and trims the root plan to a cross-cutting
overview with links.

681 lines → ~70 lines.
Resolves Task 3 review issues:
- Step 4 sub-step 4: 'trim' → 'rewrite' to signal full body replacement
  with cross-cutting overview only (per-service tasks not duplicated).
- Step 2: enumerate microservice-focus skill behavior including
  --services parsing, mirroring brainstorm.md's pattern for consistency.
…ity gate

Delegates plan execution to superpowers:executing-plans (or
subagent-driven-development if recommended). Preserves the Python
quality gate (Step 4: pytest + ruff + mypy + pre-commit loop) and
the Phase 5 PR template (Post-Deploy Monitoring + Compound
Engineered badge) — these are the wrapper's unique Python value.

Multi-service execution ordering via wavefront topology preserved.
For parallel-within-wave execution, points to
superpowers:dispatching-parallel-agents (not the deleted
orchestrating-swarms skill).

585 lines → ~140 lines.
- Step 3: explicitly instruct superpowers to skip
  finishing-a-development-branch (the wrapper owns Steps 4-5
  because it adds Python quality gate + Post-Deploy PR template).
- Step 2: add single-service mode note for execution order
  (mirrors brainstorm.md/plan.md pattern).
- Step 2: restore [Force parallel] option in the interactive
  execution plan prompt; add prose for what the option does.
- Step 5.1 / 5.2: remove '(kept; not deleted in this refactor)'
  parentheticals — runtime instructions, not author notes.
Delegates review orchestration to superpowers:requesting-code-review.
Supplies Python reviewer roster from compound-engineering.local.md,
adds conditional migration agents (data-migration-expert,
deployment-verification-agent) when PR contains migrations, and
preserves multi-service detection + per-service agent rosters.

Drops references to deleted learnings-researcher agent and the
dropped docs/solutions/ knowledge-compounding pattern. Updates
Protected Artifacts list to include docs/superpowers/specs/ and
docs/superpowers/plans/ paths.

514 lines → ~110 lines.
- Step 3: pipeline-mode safety for setup-skill fallback (when
  --services was passed, skip setup since it needs interactive
  input).
- Step 3: explicitly use Step 2's changed-service list (was
  ambiguous; an agent could re-discover from scratch).
- Step 7: restore code-simplicity-reviewer as always-on (regression
  from old workflow; the agent still exists).
- Step 6: keep legacy docs/solutions/ paths in Protected Artifacts
  so existing users with historical files don't get them flagged
  for deletion.
- Step 2: explicitly pass --services to microservice-focus (matches
  pattern in brainstorm/plan/work wrappers).
- Step 8: add default rule (file-todos by default; inline summary
  only on explicit --no-todos or user request).
These 3 commands were removed in v3.0.0. Shims print a migration
message when invoked and will be removed entirely in v4.0.0.

- /workflows:compound: no replacement (knowledge-compounding pattern
  dropped); suggests project notes or superpowers:writing-skills.
- /lfg: replaced by manual orchestration of the 4 workflow stages.
- /slfg: replaced by superpowers:dispatching-parallel-agents within
  any stage (most useful in /workflows:work).
Deleted skills (replaced by superpowers equivalents):
- brainstorming        → superpowers:brainstorming
- git-worktree         → superpowers:using-git-worktrees
- skill-creator        → superpowers:writing-skills
- create-agent-skills  → superpowers:writing-skills
- orchestrating-swarms → superpowers:dispatching-parallel-agents
- compound-docs        → none (consumer /workflows:compound also dropped)

Deleted agent:
- learnings-researcher → none (docs/solutions/ knowledge pattern dropped)
/workflows:compound was removed in v3.0.0. /setup no longer offers
or writes a 'compound' key when generating compound-engineering.local.md.
Existing user configs with a 'compound' key are ignored silently by
the wrappers (they just don't read that key).
scripts/check-dependencies.sh now scans ~/.claude/plugins for a
superpowers directory and prints an install hint if absent.
Soft check (exit 0); the actual halt happens inside each wrapper
command when superpowers:<skill> is invoked.
- plugin.json: 3.0.0 + new description (32 agents, 18 commands, 21 skills)
- CLAUDE.md: update Doc Output paths to docs/superpowers/, drop compound
  from workflow_skills YAML example, delete stale docs/solutions/ link,
  normalize <focus_context> example from connections: to dependencies:
  to match workflow commands and microservice-focus skill
- CHANGELOG.md: full v3.0.0 entry (Changed/Removed/Deprecated/Added)
  with Migration block
- README.md: update header tagline + counts, add superpowers prerequisite
  in install, remove compound/lfg/slfg from core tables (new Deprecated
  subsection), drop Swarm Mode + Knowledge Compounding sections, update
  Doc Output table to spec/plan vocabulary
Updated commands and agents that still referenced learnings-researcher,
compound-docs, orchestrating-swarms, docs/solutions/, docs/brainstorms/,
or the deleted local skills (brainstorming, git-worktree, skill-creator,
create-agent-skills). Replacements use the superpowers:* equivalent
where one exists; otherwise the reference is removed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- deepen-plan.md: check both docs/superpowers/plans/ (new) and
  docs/plans/ (legacy) for recent plans.
- check-dependencies.sh: drop misleading 'Optional' header; prefix
  each dependency with [REQUIRED] or [OPTIONAL]. superpowers is
  REQUIRED; agent-browser and rclone remain OPTIONAL.
- CHANGELOG.md: migration section now includes both 'marketplace add'
  and 'install' steps for superpowers.
- document-review/SKILL.md: fallback discovery includes the new
  docs/superpowers/plans/ path alongside legacy docs/plans/.
- CHANGELOG.md: add ### Summary line to v3.0.0 entry matching the
  established convention.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant