Superpowers
Merged opencode config + agents + accomplishments showcase — 217 skills, 17 agent profiles, 6 MCP servers, 78-server registry
npx -y skills add marktantongco/opencodelinux --skill superpowersAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Full-stack development orchestration with spec-first architecture, test-driven development, and sub-agent delegation. Use when starting any development project.
SKILL.md
2.1 KB, 390 tokens by cl100k_base, as published. Nobody here has run it
superpowers
context
Use this skill when starting any development project. It orchestrates spec‑first architecture, test‑driven development, and sub‑agent delegation — replacing a staff engineer, QA planner, and release manager in one integrated workflow.
instructions
- Specload: Before writing any code, extract or create a detailed specification (user stories, data models, figma links). Output the spec as a referenceable artifact.
- Architecture Review: Analyse the spec and design the system architecture (component tree, data flow, route design). Identify edge cases and failure points.
- Plan: Break the work into small, testable steps. Assign each step to a "sub‑agent" (e.g., "UI Agent", "API Agent").
- Test First: For each step, write the acceptance criteria and, where possible, automated tests before implementing.
- Build: Implement the code, ensuring all tests pass.
- Ship: Generate release notes, changelog, and deployment checklist. Hand off to the Deployment Manager skill if available.
constraints
- Never skip spec generation, even for small changes.
- Architecture review must happen before any code is written.
- Every step must have a clear definition of done.
- Do not merge sub‑agents; keep them independent to avoid context pollution.
examples
- Project: Build a task management app.
- Spec: User can create/update/delete tasks, tasks have due dates, drag‑and‑drop reordering.
- Architecture: React frontend with Drag & Drop context, Node.js API with SQLite, JWT auth.
- Plan: 1) Scaffold frontend and backend, 2) Implement auth, 3) Build task CRUD, 4) Add drag‑and‑drop.
- Each step tested with Vitest & Playwright before moving on.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.