weorbitant · BaronVonSario · May 25, 2026 · May 25, 2026 · May 25, 2026 · May 25, 2026
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "compound-engineering-feat-python",
-  "version": "2.5.2",
-  "description": "Python-specialized development tools with microservice support. 33 agents, 21 commands, 26 skills, 1 MCP server.",
+  "version": "3.0.0",
+  "description": "Python-specialized development tools with microservice support, built on superpowers. 32 agents, 18 commands, 21 skills, 1 MCP server.",
   "hooks": {
     "SessionStart": [
       {

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,6 +5,71 @@ All notable changes to the compound-engineering-feat-python plugin will be docum
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.0.0] - 2026-05-25
+
+### Changed
+- Plugin now requires the `superpowers` plugin as a foundation. All generic workflow
+  primitives (brainstorming, planning, execution, review, git worktrees, parallel
+  agents, skill writing) are delegated to superpowers; this plugin focuses on
+  Python/Django/FastAPI domain value and microservice orchestration.
+- Workflow commands rewritten as thin wrappers that delegate to superpowers skills:
+  `/workflows:brainstorm` → `superpowers:brainstorming`, `/workflows:plan` →
+  `superpowers:writing-plans`, `/workflows:work` → `superpowers:executing-plans`
+  (+ Python quality gate), `/workflows:review` → `superpowers:requesting-code-review`.
+- Microservice Focus Gate logic extracted from each workflow command into a new
+  `microservice-focus` skill.
+- Brainstorm artifact paths changed from `docs/brainstorms/` to
+  `docs/superpowers/specs/` (and `{service}/docs/superpowers/specs/` in multi-service
+  mode), matching superpowers vocabulary ("spec" instead of "brainstorm doc").
+- `scripts/check-dependencies.sh` now warns if the superpowers plugin is not detected.
+- `<focus_context>` block in `CLAUDE.md` normalized from `connections:` (single line)
+  to `dependencies:` (list format), matching the workflow commands and the
+  `microservice-focus` skill.
+
+### Removed
+- `/workflows:compound` command (knowledge-capture pattern dropped). Deprecation shim
+  remains for one major cycle.
+- `/lfg` and `/slfg` autonomous pipelines (users orchestrate stages directly).
+  Deprecation shims remain for one major cycle.
+- 6 skills replaced by superpowers equivalents: `brainstorming`, `git-worktree`,
+  `skill-creator`, `create-agent-skills`, `orchestrating-swarms`, and `compound-docs`
+  (the last because its only consumer was `/workflows:compound`).
+- `learnings-researcher` agent (read from the now-removed `docs/solutions/` pattern).
+- Knowledge-compounding pattern (`docs/solutions/`) — historical files in user repos
+  remain untouched (and `/workflows:review` still protects them from accidental
+  deletion) but are no longer read or written by this plugin.
+- `compound` key from `workflow_skills` in `compound-engineering.local.md` schema.
+  Existing keys are silently ignored.
+
+### Deprecated
+- `/lfg`, `/slfg`, `/workflows:compound` exist as shims that print a migration message
+  when invoked. They will be removed entirely in v4.0.0.
+
+### Added
+- `microservice-focus` skill consolidating service discovery, `--services` parsing,
+  multi-service prompting via `AskUserQuestion`, and `<focus_context>` block construction.
+
+### Migration
+- Install superpowers:
+  ```
+  /plugin marketplace add anthropics/claude-plugins-official
+  /plugin install superpowers@claude-plugins-official
+  ```
+- Replace any `/lfg`, `/slfg`, or `/workflows:compound` invocations with the
+  appropriate sequence of `/workflows:brainstorm` → `/workflows:plan` →
+  `/workflows:work` → `/workflows:review` (or `superpowers:dispatching-parallel-agents`
+  within stages for parallel work).
+- Move any documents under `docs/brainstorms/` to `docs/superpowers/specs/` if you
+  want them auto-discovered by `/workflows:plan` (path-only rename; no schema change).
+- Remove the `compound:` line from your project's `compound-engineering.local.md`
+  if present (harmless to leave, but cleaner to drop).
+
+### Summary
+
+32 agents, 18 active commands (+ 3 deprecation shims for one major cycle), 21 skills, 1 MCP server. Requires the `superpowers` plugin.
+
+---
+
 ## [2.5.2] - 2026-04-20
 
 ### Changed

diff --git a/CLAUDE.md b/CLAUDE.md
@@ -48,13 +48,12 @@ skills/
 - `/workflows:plan` - Create implementation plans
 - `/workflows:review` - Run comprehensive code reviews
 - `/workflows:work` - Execute work items systematically
-- `/workflows:compound` - Document solved problems
 
 **Why `workflows:`?** Claude Code has built-in `/plan` and `/review` commands. Using `name: workflows:plan` in frontmatter creates a unique `/workflows:plan` command with no collision.
 
 ## Skill Compliance Checklist
 
-When adding or modifying skills, verify compliance with skill-creator spec:
+When adding or modifying skills, verify compliance with the official skill spec (see `superpowers:writing-skills`):
 
 ### YAML Frontmatter (Required)
 
@@ -102,11 +101,12 @@ When spawning sub-agents via Task tool, include a standardized `<focus_context>`
 ```
 <focus_context>
   services: service-a (./service-a), service-b (./service-b)
-  connections: service-a depends on lib-common (pyproject.toml)
+  dependencies:
+    - service-a depends on lib-common (shared DTOs)
 </focus_context>
 ```
 
-All commands and skills MUST include this block when spawning sub-agents to prevent focus loss in nested delegation chains.
+All commands and skills MUST include this block when spawning sub-agents to prevent focus loss in nested delegation chains. The full Focus Gate protocol and `<focus_context>` template now live in the `microservice-focus` skill. Workflow commands invoke that skill once instead of inlining the logic.
 
 ### Pipeline Mode
 
@@ -119,9 +119,8 @@ All workflow commands accept `--services` argument for automated invocation:
 
 | Doc Type | Single Service | Cross-Service |
 |----------|---------------|---------------|
-| Brainstorms | Single doc mentioning affected services | `{service}/docs/brainstorms/...` per service |
-| Plans | `{service}/docs/plans/...` | Root overview + per-service plan files |
-| Solutions | `{service}/docs/solutions/...` | Root `docs/solutions/...` with service refs |
+| Specs | `docs/superpowers/specs/...` | `{service}/docs/superpowers/specs/...` per service |
+| Plans | `docs/superpowers/plans/...` (or `{service}/docs/superpowers/plans/...`) | Root overview at `docs/superpowers/plans/...` + per-service plan files |
 
 ## Workflow Skills Configuration
 
@@ -134,7 +133,6 @@ workflow_skills:
   plan: [django-patterns]
   work: [django-patterns, pytest-patterns]
   review: [django-patterns, pytest-patterns]
-  compound: [django-patterns]
 ---
 ```
 
@@ -149,6 +147,3 @@ Project-local skills in `.claude/skills/` can also be listed here by name.
 - If the user asks for something that will cause problems (bad architecture, wrong pattern, fragile code), push back before implementing.
 - Be direct and honest, even if it means disagreeing. A wrong decision caught early saves hours of rework.
 
-## Documentation
-
-See `docs/solutions/plugin-versioning-requirements.md` for detailed versioning workflow.
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 # Compound Engineering feat. Python
 
-A Claude Code plugin that supercharges Python development with 33 specialized agents, 21 commands, 26 skills, and an MCP server — all wired into a cohesive engineering workflow. Built for Django, FastAPI, pytest, Pydantic, PostgreSQL, and PostGIS projects, with first-class support for multi-service monorepos.
+A Claude Code plugin that supercharges Python development with 32 specialized agents, 18 commands, 21 skills, and an MCP server — built on Anthropic's `superpowers` plugin for workflow primitives. Specialized for Django, FastAPI, pytest, Pydantic, PostgreSQL, and PostGIS projects, with first-class support for multi-service monorepos.
 
 > Fork of [Compound Engineering Plugin](https://github.com/EveryInc/compound-engineering-plugin) by [Kieran Klaassen](https://github.com/kieranklaassen), fully rewritten for the Python ecosystem.
 
@@ -9,15 +9,22 @@ A Claude Code plugin that supercharges Python development with 33 specialized ag
 Instead of generic AI assistance, this plugin gives Claude deep knowledge of Python frameworks and enforces a structured engineering workflow:
 
 ```
-/workflows:brainstorm → /workflows:plan → /workflows:work → /workflows:review → /workflows:compound
+/workflows:brainstorm → /workflows:plan → /workflows:work → /workflows:review
 ```
 
 Each step loads relevant skills (Django patterns, pytest conventions, PostgreSQL optimization...), spawns specialized review agents, and enforces quality gates — tests must pass, linting must be clean, pre-commit hooks must succeed — before anything ships.
 
-For the impatient: `/lfg` runs the entire pipeline autonomously, from plan to PR.
-
 ## Installation
 
+### Prerequisite: Install superpowers
+
+This plugin requires the `superpowers` plugin (provides generic workflow primitives).
+
+```
+/plugin marketplace add anthropics/claude-plugins-official
+/plugin install superpowers@claude-plugins-official
+```
+
 This plugin is distributed as its own Claude Code marketplace. Add the repo, then install:
 
 ```
@@ -51,29 +58,24 @@ Checked automatically on session start — you'll see warnings for anything miss
 /workflows:plan add rate limiting with Redis sliding window
 
 # Execute the plan
-/workflows:work docs/plans/2026-04-01-rate-limiting.md
+/workflows:work docs/superpowers/plans/2026-04-01-rate-limiting.md
 
 # Review the changes
 /workflows:review
-
-# Document what you learned
-/workflows:compound
-
-# Or just do it all at once
-/lfg add rate limiting to the payment API
 ```
 
+Brainstorm specs land at `docs/superpowers/specs/`; plans at `docs/superpowers/plans/`.
+
 ## Core Workflow Commands
 
 Commands use `workflows:` prefix to avoid collisions with Claude Code built-ins (`/plan`, `/review`).
 
 | Command | Purpose |
 |---------|---------|
-| `/workflows:brainstorm` | Explore requirements and approaches before committing to a plan |
-| `/workflows:plan` | Generate implementation plans with size-appropriate detail |
-| `/workflows:work` | Execute a plan with incremental commits, quality gates, and test-fix loops |
-| `/workflows:review` | Multi-agent code review with configurable reviewer roster |
-| `/workflows:compound` | Capture solved problems as searchable documentation in `docs/solutions/` |
+| `/workflows:brainstorm` | Explore requirements before planning (delegates to `superpowers:brainstorming`) |
+| `/workflows:plan` | Generate implementation plans (delegates to `superpowers:writing-plans`) |
+| `/workflows:work` | Execute a plan with Python quality gates (delegates to `superpowers:executing-plans`) |
+| `/workflows:review` | Multi-agent Python code review (delegates to `superpowers:requesting-code-review`) |
 
 Each workflow command:
 - Loads project-specific skills from `compound-engineering.local.md` configuration
@@ -84,8 +86,6 @@ Each workflow command:
 
 | Command | Description |
 |---------|-------------|
-| `/lfg` | Full autonomous pipeline: plan → deepen → work → review → test → video → PR |
-| `/slfg` | Same as `/lfg` but uses swarm mode for parallel execution |
 | `/deepen-plan` | Enrich a plan with parallel research agents for each section |
 | `/changelog` | Generate changelogs from recent merges |
 | `/create-agent-skill` | Guided skill creation |
@@ -101,7 +101,16 @@ Each workflow command:
 | `/report-bug` | Report a plugin bug |
 | `/heal-skill` | Fix skill documentation issues |
 
-## Agents (33)
+### Deprecated commands (v3.0.0)
+
+These commands were removed in v3.0.0; they remain as shims that print a migration message and will be deleted in v4.0.0:
+
+- `/workflows:compound` — knowledge-capture pattern dropped; no replacement.
+- `/lfg`, `/slfg` — autonomous pipelines dropped; orchestrate stages directly.
+
+See CHANGELOG.md v3.0.0 for migration details.
+
+## Agents (32)
 
 Agents run as sub-processes during workflows. They are grouped by specialization.
 
@@ -169,7 +178,6 @@ Agents use a 3-tier model strategy to optimize cost without sacrificing quality:
 | `best-practices-researcher` | sonnet | External best practices (checks skills first) |
 | `framework-docs-researcher` | sonnet | Framework documentation and patterns |
 | `git-history-analyzer` | sonnet | Git history and code evolution |
-| `learnings-researcher` | haiku | Past solutions from `docs/solutions/` |
 | `repo-research-analyst` | sonnet | Repository structure and conventions |
 
 ### Design
@@ -189,10 +197,12 @@ Agents use a 3-tier model strategy to optimize cost without sacrificing quality:
 | `pr-comment-resolver` | sonnet | PR comment resolution |
 | `spec-flow-analyzer` | opus | User flow gap analysis |
 
-## Skills (26)
+## Skills (21)
 
 Skills provide domain knowledge that agents and workflows load on demand. They contain reference documentation, conventions, and patterns.
 
+Workflow primitives (brainstorming, git worktrees, skill writing, parallel agents) now come from the `superpowers` plugin.
+
 ### Python Core
 - **`python-style`** — PEP 8, naming, imports, logging with emoji prefixes
 - **`python-typing`** — Type hints, Pydantic v2, Protocol, generics
@@ -217,23 +227,18 @@ Skills provide domain knowledge that agents and workflows load on demand. They c
 - **`agent-native-architecture`** — Agent-native app patterns (action parity, context injection, shared workspace, dynamic capability discovery)
 - **`frontend-design`** — Production-grade frontend interfaces
 
+### Microservice Support
+- **`microservice-focus`** — Service discovery, `--services` parsing, multi-service prompting, and `<focus_context>` block construction
+
 ### Development Tools
-- **`compound-docs`** — Structured solution documentation
-- **`create-agent-skills`** — Skill authoring guide
-- **`skill-creator`** — Skill creation framework
 - **`setup`** — Interactive project configuration for review agents and workflow skills
 
 ### Content & Workflow
-- **`brainstorming`** — Collaborative exploration techniques
 - **`commit`** — Conventional commits with gitmoji, logical grouping, pre-commit handling
 - **`document-review`** — Structured document improvement
 - **`file-todos`** — File-based todo tracking
-- **`git-worktree`** — Parallel development with Git worktrees
 - **`resolve-pr-parallel`** — Parallel PR comment resolution
 
-### Multi-Agent Orchestration
-- **`orchestrating-swarms`** — Multi-agent coordination with TeammateTool and Task system
-
 ### Integrations
 - **`rclone`** — Cloud storage uploads (S3, R2, B2)
 - **`agent-browser`** — CLI browser automation via Vercel's agent-browser
@@ -275,7 +280,6 @@ workflow_skills:
   plan: [django-patterns]
   work: [django-patterns, pytest-patterns]
   review: [django-patterns, pytest-patterns]
-  compound: [django-patterns]
 ---
 ```
 
@@ -289,7 +293,7 @@ The `/setup` skill auto-detects your stack (Django, FastAPI, DRF, Celery, SQLAlc
 
 ## Microservice Support
 
-For multi-service monorepos, the plugin provides:
+For multi-service monorepos, the plugin provides. Focus Gate logic now lives in the `microservice-focus` skill, invoked once by each workflow command.
 
 - **Auto-detection** — Discovers services via `*/pyproject.toml` at root level
 - **Focus Gate** — Each workflow command prompts for relevant services (or accepts `--services` argument)
@@ -309,9 +313,8 @@ All workflow commands accept `--services` for automated invocation:
 
 | Doc Type | Single Service | Multi-Service |
 |----------|---------------|---------------|
-| Brainstorms | Single document | `{service}/docs/brainstorms/` per service |
-| Plans | `docs/plans/` | Root overview + per-service plan files |
-| Solutions | `docs/solutions/` | `{service}/docs/solutions/` with cross-refs |
+| Specs | `docs/superpowers/specs/` | `{service}/docs/superpowers/specs/` per service |
+| Plans | `docs/superpowers/plans/` | Root overview + per-service plan files under `{service}/docs/superpowers/plans/` |
 
 ## How It Works
 
@@ -326,25 +329,11 @@ The work command is the engine that turns plans into shipped code:
 
 Every commit goes through a test-and-fix gate: run tests → fix failures → stage → commit → if pre-commit fails → fix → re-test → retry. Never ships with failing tests, never skips hooks.
 
-### Swarm Mode
-
-For complex features, `/slfg` or explicit swarm mode spawns parallel worker agents:
-
-```
-Team lead → spawns implementers + testers → monitors via Task system → ships when done
-```
-
-Uses Claude Code's TeammateTool system with dependency-aware task scheduling.
-
-### Knowledge Compounding
-
-`/workflows:compound` captures solutions in `docs/solutions/` with YAML frontmatter. The `learnings-researcher` agent searches these during future reviews, so past solutions inform new work. Knowledge compounds.
-
 ## Version History
 
 See [CHANGELOG.md](CHANGELOG.md) for detailed version history.
 
-**Current version: 2.4.0**
+**Current version: 3.0.0**
 
 ## Contributing
 

diff --git a/agents/research/best-practices-researcher.md b/agents/research/best-practices-researcher.md
@@ -40,9 +40,9 @@ Before going online, check if curated knowledge already exists in skills:
    - FastAPI → `fastapi-patterns`, `fastapi-sqlalchemy`
    - Frontend/Design → `frontend-design`, `swiss-design`
    - TypeScript/React → `react-best-practices`
-   - AI/Agents → `agent-native-architecture`, `create-agent-skills`
-   - Documentation → `compound-docs`, `every-style-editor`
-   - File operations → `rclone`, `git-worktree`
+   - AI/Agents → `agent-native-architecture`
+   - Documentation → `every-style-editor`
+   - File operations → `rclone`
    - Image generation → `gemini-imagegen`
 
 3. **Extract Patterns from Skills**:

diff --git a/agents/research/git-history-analyzer.md b/agents/research/git-history-analyzer.md
@@ -56,4 +56,4 @@ When analyzing, consider:
 
 Your insights should help developers understand not just what the code does, but why it evolved to its current state, informing better decisions for future changes.
 
-Note that files in `docs/plans/` and `docs/solutions/` are compound-engineering pipeline artifacts created by `/workflows:plan`. They are intentional, permanent living documents — do not recommend their removal or characterize them as unnecessary.
+Note that files in `docs/plans/` are compound-engineering pipeline artifacts created by `/workflows:plan`. They are intentional, permanent living documents — do not recommend their removal or characterize them as unnecessary.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -56,4 +56,4 @@ When analyzing, consider:

		Your insights should help developers understand not just what the code does, but why it evolved to its current state, informing better decisions for future changes.

		Note that files in `docs/plans/` and `docs/solutions/` are compound-engineering pipeline artifacts created by `/workflows:plan`. They are intentional, permanent living documents — do not recommend their removal or characterize them as unnecessary.
		Note that files in `docs/plans/` are compound-engineering pipeline artifacts created by `/workflows:plan`. They are intentional, permanent living documents — do not recommend their removal or characterize them as unnecessary.