Superpowers · 软件开发

用可组合的开发 Skills,引导编程 Agent 完成设计、规划、实现、调试与评审。

Superpowers 提供 15 个可组合的软件开发 Skills。本合集收录仓库的完整技能目录,保留配套文件和技能间引用。各工具的插件启动机制与集成文件仍属于上游项目。

适用场景

  • 设计与实现新功能
  • 调试并验证修复
  • 规划任务与评审改动

使用方法

先用 brainstorming 澄清需求,再规划工作,选择直接实现或子 Agent 实现。按需要使用测试、调试与评审技能。需要官方针对各工具的插件集成时,按照来源仓库的安装指南操作。

Skills

  • brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    obra/superpowers
  • diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    obra/superpowers
  • dispatching-parallel-agents

    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    obra/superpowers
  • executing-plans

    Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

    obra/superpowers
  • finishing-a-development-branch

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    obra/superpowers
  • receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    obra/superpowers
  • requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    obra/superpowers
  • subagent-driven-development

    Use when executing implementation plans with independent tasks in the current session

    obra/superpowers
  • systematic-debugging

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    obra/superpowers
  • test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

    obra/superpowers
  • using-git-worktrees

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    obra/superpowers
  • using-superpowers

    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    obra/superpowers
  • verification-before-completion

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    obra/superpowers
  • writing-plans

    Use when you have a spec or requirements for a multi-step task, before touching code

    obra/superpowers
  • writing-skills

    Use when creating new skills, editing existing skills, or verifying skills work before deployment

    obra/superpowers