Combine superpowers' full workflow with mattpocock's precision — engineered via superpowers-overrides.
Personal Claude Code plugin marketplace. Three plugins work together as one pipeline: brainstorm, plan, build, ship.
Superpowers is the full stack — brainstorming, writing plans, subagent-driven development, verification, branch finish. One library, end to end.
mattpocock-skills is the precision layer — grilling for hard questions, tdd for implementation, to-tickets for slicing work. Small surface, sharp tools.
Neither alone told me when to delegate, how to review specs, or how to phase a large feature. superpowers-overrides sits in front of upstream superpowers skills: intercept, replace or delegate, and wire mattpocock in at the right step. For big scope it adds overall + phase — decompose in an overall spec, then run full spec → plan → dev cycles one phase at a time.
Overall spec → Phase spec → Plan → SDD/TDD → Verify → Ship
Overrides add grilling and subagent review at design time; mattpocock handles grilling, tdd, and to-tickets via delegation.
Skill mapping and harness setup → superpowers-overrides README.
# In Claude Code
/plugin marketplace add oscaner/skills
/plugin install mattpocock-skills@oscaner
/plugin install superpowers@oscaner
/plugin install superpowers-overrides@oscanerClone this repo (submodule required for local development):
git clone https://github.com/Oscaner/skills.git
cd skills
git submodule update --init- Install
superpowers,superpowers-overrides, andmattpocock-skillsfrom the marketplace. - Run the init skill once per project — re-run after plugin upgrades. Slash command depends on your harness → Usage.
- Invoke the superpowers workflow as you normally would — overrides intercept and run first.
superpowers-overrides README — skills by phase, Claude Code vs Cursor, enforcement layers.
After editing overrides: pnpm run generate:overrides && pnpm run emit && pnpm run validate.
Branch flow: develop is the default integration branch — day-to-day PRs merge here and accumulate changesets. Production releases land on main only via a develop → main PR (enforced by CI and GitHub Rulesets). Version PRs, git tags, and GitHub Releases run on main only; an automated main → develop sync PR keeps develop aligned after release.
Release: .changeset/README.md. Contributor pattern: CLAUDE.md.
First-party code (superpowers-overrides, marketplace tooling) is MIT.
Vendored plugins keep their own licenses — see each plugin directory (e.g. plugins/mattpocock-skills/LICENSE).