superpowers-gstack

Superpowers + GStack: Routing, Context Management & Workflow

"Superpowers owns the implementation loop, GStack owns everything before and after it. Context Guard keeps the session clean."

A Claude Code plugin that integrates Superpowers and GStack into one workflow — with skill routing, automatic context management, and project auto-configuration. Already have an existing project? Run /adapt and it analyzes your setup, preserves your CLAUDE.md, and adds routing — so you can jump right in.

Status: Work in Progress — Actively developed. Contributions, feedback, and ideas are very welcome. See Contributing.

What problem does this solve?

If you've installed both Superpowers and GStack, you've probably run into these issues:

• Claude picks the wrong framework for the task (GStack's /investigate when you wanted Superpowers' debugging)
• No clear handoff between planning (GStack) and implementation (Superpowers)
• Context rot in long sessions — quality degrades as the context window fills up
• You don't know which skills to use when, or which to skip for your project type

This project solves all of that with routing rules, automatic context management, and a structured 4-phase workflow.

Why Both?

Every comparison article says "use both" but nobody explains how. This project fills that gap:

Framework	Strengths	Phase
GStack (Garry Tan)	Product thinking, architecture review, QA, security, shipping	Planning, Review, Ship
Superpowers (Jesse Vincent)	TDD, structured coding, debugging, code review	Implementation

They never overlap. GStack focuses on what roles review the work. Superpowers focuses on how code gets written.

What's Included

• Claude Code Plugin with twelve skills:
  • /setup-routing — Generates a tailored CLAUDE.md for new projects
  • /adapt — Adds routing to existing projects without losing your CLAUDE.md content
  • /autoimplement — Auto-advance through a multi-phase implementation plan by chaining /review, /pitfall-verification, and /codex review at each phase boundary. Skips the y/n prompts you'd always answer "yes" to when reviews pass. Active pre-flight (v2.14.0+, tightened in v2.14.2): unless the latest commit touching the plan path matches the pre-flight marker regex ^(chore|fix)\(plan\):[[:space:]]*pre-flight([[:space:]]|$), autoimplement itself runs pitfall + codex on the plan body before Phase 1 dispatch — closes the gap between /writing-plans and autonomous execution. The pre-flight step commits a marker (chore(plan): pre-flight reviewed clean (...) or fix(plan): pre-flight {reviews_ran} feedback) so subsequent runs skip it. Stops by default when any review flags actionable issues; severe findings (security/data-loss/correctness in test assertions) always stop regardless of policy; pitfall/codex per-phase findings can be treated as advisory via the upfront policy question. Hard refusals: fewer than 2 phases, missing per-phase commit steps, dirty working tree, on main/master branch, plan touches migrations / secrets / credentials / .env / .ssh.
  • /context-handoff — Writes a human-readable handoff to docs/superpowers/handoff.md before /clear or /compact. Auto-resumes on next session start. Different from gstack's /context-save — this lives in the repo and works cross-machine.
  • /htmlify — Generates beautiful, pedagogical HTML companions for MD artefakter (design docs, plans, handoffs). v2 (2.0.0): opt-in --plan flag aktiverer rich rendering med 9 visuelle komponenter (comparison-matrix, flowchart-svg, pullquote, callout-box, stats-bar, two-column, expandable, diff-card, feedback-panel). Plan'en genereres av Claude Code i samme sesjon (Max-plan compute — ingen Anthropic API-kall). Uten --plan: v1-template-rendering (backwards compatible). Auto-opens via --open flag (macOS); aggregated per-directory dashboard via htmlify dashboard <dir>. Optional PostToolUse hook auto-fires on artifact writes. Bun + TypeScript; 138 unit tests; sanitized via DOMPurify.
  • /pitfall-verification — Final-check skill run after any PRD, spec, plan, or code artifact. Targeted check that typical pitfalls for that artifact type and domain (security, idempotency, contracts, edge cases, LLM output) actually do not apply. Two rounds max.
  • /quality-review — Perceived-quality gate run after a PRD, spec, or implementation plan, before implementation begins. Hunts pitfalls that make a product feel cheap or broken even when it technically works (silent failures, missing loading/empty states, error recovery, state drift, animations, AI output, sudo flows). Complementary to /pitfall-verification: that one asks "will this work?", this one asks "will this feel good?".