-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Composing superpowers with team-specific skills #1007
Description
- I searched existing issues and this has not been proposed before
What problem does this solve?
I use superpowers alongside team-specific skills (on-call triage, infrastructure runbooks, MCP server configs for internal tools). Both use the same format — SKILL.md with YAML frontmatter — but they install through separate mechanisms and there's no way to compose them. Onboarding a teammate means walking them through two install flows, and there's no declarative way to say "use these superpowers skills plus these team skills."
I've ended up encoding some of your patterns into my own essentials pack — verification-before-completion, code-reviewer, and similar — because I couldn't compose with superpowers directly. I'd rather point at the original than maintain derivatives that drift.
Proposed solution
I built aipack to solve this problem — it composes content from multiple sources and syncs it to Claude Code, Codex, Cline, and OpenCode. Superpowers' content already uses the exact format aipack expects. Adding a pack.json to the repo root would make superpowers installable alongside other packs:
{
"schema_version": 1,
"name": "superpowers",
"version": "5.0.6",
"root": "."
}One metadata file, no changes to existing content or distribution. I tested this locally — all 14 skills and the code-reviewer agent rendered to all four harnesses, composed with my team's content. Nothing in superpowers needed modification.
What alternatives did I consider?
Wrapper pack in my registry. I can maintain a pointer to superpowers externally. Works, but version tracking becomes my problem.
Keep encoding derivatives. What I do now. It works, it's the wrong approach.
Is this appropriate for core Superpowers?
Genuinely unsure. It's one metadata file and purely additive — but it is a third-party tool integration. If your preference is that this lives outside the repo, I'll maintain it as a wrapper and that's fine. Raising it here because the format compatibility is already there and the composition use case is real.
Context
- aipack v0.13.0
- Tested with superpowers v5.0.6
- Harnesses: Claude Code, Codex CLI, Cline, OpenCode