Skip to content

Chapter 25 · Three Skills Repositories Compared ​

Chapter goals: Place mattpocock/skills, obra/superpowers, and Fission-AI/OpenSpec side by side; understand their respective engineeringphilosophy and applicable scenarios; make selection judgments in real projects.

25.1 Positioning Differences Among the Three Repos ​

Dimensionmattpocock/skillsobra/superpowersFission-AI/OpenSpec
Philosophy"Small and改-able, anti-framework takeover""Skills auto-trigger;端到端 run through""Spec is the artifact; fluid not rigid"
Core claimKeep skills小, replaceable,改-ableProvide a complete development methodology; skills激活 on-demand变更即文档; spec-driven drives development
Install methodClaude Code plugin or skills.shpip install superpowers@fission-ai/openspec CLI
Typical scenarioInject a set of high-quality skills into an existing projectFrom零 to delivering a feature (including TDD)Drive变更 in brownfield projects
Relation to the standardFollows the Agent Skills specFollows the spec; skills auto-triggerIndependent route; /opsx command flow

25.2 mattpocock/skills: Real Skills for Engineers ​

Philosophy ​

Matt Pocock (author of Total TypeScript) explicitly反对 GSD, BMAD, Spec-Kit这类 "takeover the development process" frameworks:

"Approaches like GSD, BMAD, and Spec-Kit try to help by owning the process. But while doing so, they take away your control and make bugs in the process hard to resolve."

His solution: keep skills small, replaceable, and改-able.

Two Install Philosophies ​

bash
# Method 1: Claude Code official plugin (subscription-based, read-only)
claude plugins install mattpocock-skills

# Method 2: skills.sh to复制 an editable copy
npx skills@latest add mattpocock/skills
# Interactively pick the skills you want

The former suits "using the latest stable version"; the latter suits "I want to改 the skill content to适配 my project."

Selection Advice ​

  • ✅ Suitable for: wantingplug-and-play high-quality skills;不想维护一整套 methodology
  • ⚠️ Limitation: you need to自行 decide when and which skills to use; no强制流程

25.3 obra/superpowers: End-to-End Methodology ​

Philosophy ​

Superpowers claims to be a "complete software development methodology for your coding agents". The core selling point: skills auto-trigger;端到端 run through.

Six-Step Workflow ​

text
brainstorming → using-git-worktrees → writing-plans
     → subagent-driven-development / executing-plans
     → test-driven-development → requesting-code-review

Each step is a skill;triggered in order:

  1. Brainstorming: don't write code first; let the agent打磨 ideas through Q&A; output a design doc;
  2. Using Git Worktrees: create isolated worktrees for each任务; keep the main branch stable;
  3. Writing Plans:拆 the design into 2–5 minute sub-tasks; each with precise file paths and verification steps;
  4. Subagent-Driven Development:派 an独立 subagent for each sub-task;经过两阶段审查;
  5. Test-Driven Development:强制 RED-GREEN-REFACTOR;
  6. Requesting Code Review: insert a review环节 between tasks; blocking bugs阻止 the next step.

Selection Advice ​

  • ✅ Suitable for: teams wanting "zero-config端到端 run through"; complex features needing系统化拆解
  • ⚠️ Limitation: introduces较多约束 (worktree/TDD/review); not suitable for快速 prototypes or探索性 experiments

25.4 Fission-AI/OpenSpec: Spec-Driven Development ​

Philosophy ​

OpenSpec's core philosophy: "→ fluid not rigid, → iterative not waterfall, → easy not complex". It doesn't作 skills the focus; instead it makes the "spec" (specification) the第一公民 driving development.

/opsx Command Flow ​

bash
# Explore requirements
/opsx:explore "I want to加 a dark theme to the project"

# Propose a formal变更
/opsx:propose add-dark-mode

# Apply the变更
/opsx:apply add-dark-mode

# Archive after完成
/opsx:archive add-dark-mode

Each propose生成 a proposal.md under openspec/changes/<name>/:

markdown
# Proposal: Add Dark Mode

## Why
User feedback:夜间使用疲劳; improve readability.

## What Changes
- New CSS variables `--bg-color` / `--text-color`
- Add系统偏好 detection (prefers-color-scheme)
- Provide a manual toggle button

## Impact
-涉及: src/theme.ts, styles.css
-不影响: business逻辑层

Selection Advice ​

  • ✅ Suitable for: large teams with stable products needing严格变更 tracking; brownfield project改造
  • ⚠️ Limitation: the /opsx command依赖特定的 agent integration; may feel重 for greenfield projects

25.5 Collaborative Combination of the Three ​

In real工程, these three tools are often not a单选 but a组合:

text
[OpenSpec] ← governs "what to do" (specs and decisionrecords)
    ↓
[Superpowers] ← governs "how to do it" (complete workflowdriven)
    ↓
[mattpocock/skills] ← governs "detail optimization" (daily coding辅助)

A typical combined场景:

  1. Use OpenSpec to发起 a变更 proposal;产出 a proposal.md;
  2. Use Superpowers to跑 brainstorm → plan → TDD完整的循环;
  3. Duringdaily coding, use mattpocock's skills for code review, commit helpers, and other daily辅助.

All三条路线 respect the Agent Skills spec's discovery and loading mechanism; they can共享 in the same .pi/skills/ directory and协同工作.

Chapter Summary ​

  • mattpocock/skills: small and改-able skill collection; anti-framework philosophy; two install methods
  • obra/superpowers: complete development methodology; skills auto-trigger; six-step workflow covering brainstorm to review
  • Fission-AI/OpenSpec: spec-driven; /opsx command flow;变更即工件;专为 brownfield designed
  • The three are not mutually exclusive;可组合使用 per scenario; all遵循 the Agent Skills spec's progressive disclosure spirit

🧪 随堂测验

点击你认为正确的选项。答错时会展示正确答案与原因解析。

1. What is the核心理念 difference between the two install methods of mattpocock/skills?

2. In Superpowers' six-step workflow, which step负责强制 RED-GREEN-REFACTOR?

3. Which of the following is NOT included in OpenSpec's core design philosophy?

4. In a brownfield project, which component is most适合 prioritizing introduction?

🛠️ Hands-on Practice ​

  1. Pick any one skill from mattpocock/skills (e.g. commit-helper); install it into your project with npx skills@latest add; observe the触发 timing.
  2. Install Superpowers with pip install superpowers;跑 a brainstorming流程; record the output.
  3. Run /opsx:explore and /opsx:propose in anexisting repo;理解 the proposal.md生成 structure.

After completing the exercises, proceed to Next chapter: Loop Engineering: From Prompts to Loops.