158 skills · sorted by relevance
Examine superpowers session records to document repeated work, departures from plans, delays, and token usage. Produce an evidence-based report with file and line references, and prepare bug-report material when requested.
Review AI agent session logs to document repeated work, departures from plans, delays, and token usage. Produce an evidence-based report with file and line references, and prepare a bug report when appropriate.
Guide an agent to check and invoke relevant skills before replying or taking action. It sets the order for choosing workflow and implementation skills, with reference guides for adapting the process to different agent environments.
Carry out a written implementation plan in a separate session, reviewing it before starting and tracking each task through verification. The workflow pauses for blockers and hands completed work to a development branch finishing process.
Establish a routine for checking and invoking relevant skills before answering or taking action. It prioritizes skills that define the workflow, then guides the agent toward task-specific skills and any checklists they contain.
Turn specifications into detailed implementation plans before coding. Break work into testable tasks with exact file paths, code, test commands, expected results, and interfaces so another developer or agent can carry out the work.
Legacy compatibility entry for prompts or documentation that explicitly name `using-superpowers`. Route new skill-discovery workflows to `using-skills`; do not activate both entrypoints for the same task.
The English summary is being prepared. Showing the original description.
Create, revise, and validate agent skills through tests that compare behavior with and without the instructions. It helps identify unclear guidance, choose an appropriate document structure, and refine wording before deployment.
Clarifies the purpose, preferences, and constraints of a new feature or project through conversation. When useful, it offers mockups or temporary prototypes, then captures an agreed description or written design before implementation begins.
Turn specifications or requirements into an implementation plan before coding begins. Break work into testable tasks with exact files, function definitions, test assertions, and verification commands, so another developer or agent can follow the plan.
Turn a feature idea into a design document through focused dialogue. The skill clarifies goals and constraints, compares two or three approaches, and reviews the design in sections before documenting architecture, data flow, errors, and testing.
Turn development requirements into an implementation plan with specific files, function signatures, tests, and verification commands. Use it before coding to document decisions and divide the work into independently testable tasks.
Guides an agent in choosing and invoking relevant skills before responding or acting. It defines workflow priorities, points to environment-specific references, and distinguishes reference skills that should load only when explicitly requested.
Investigate bugs, failing tests, and unexpected behavior before proposing changes. Follow four stages to gather evidence, compare working examples, test a specific cause, and verify a focused fix with a test that reproduces the problem.
Sync local skills repository with upstream changes from obra/superpowers-skills
The English summary is being prepared. Showing the original description.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
The English summary is being prepared. Showing the original description.
Stack Honey onto Superpowers-style workflows (subagent-driven-development, dispatching-parallel-agents, executing-plans) and any orchestration that dispatches fresh subagents. Dispatched subagents run in isolated context and do NOT inherit the session's Honey hook, so they emit full-fat code and verbose reports. Use when you are about to dispatch implementer/reviewer/fixer/parallel subagents: it gives the exact Honey directive to paste into each dispatch prompt, with a worker variant and a reviewer variant, so the levers apply inside the subagents too — where the multiplied cost actually is.
The English summary is being prepared. Showing the original description.
Stack Honey onto Superpowers-style subagent workflows: dispatched subagents skip the session hook, so inject the levers into each dispatch prompt.
The English summary is being prepared. Showing the original description.
Routes a Superpowers plan file through the /work-backlog-item pipeline and writes SAM task back-references and chunk annotations into the original plan. Use when given a path to a Superpowers plan file via $ARGUMENTS and needing to create a linked backlog item plus SAM task plan.
The English summary is being prepared. Showing the original description.
Use when writing Swift code for Apple platforms - iOS, macOS, visionOS. Covers Swift 6 concurrency, actors, Sendable, async/await, SwiftUI, MVVM architecture, Metal GPU programming, RealityKit ECS, visionOS scenes, interpolation/animation, advanced collection types, property wrappers, Combine bridging, error handling, testing, and API design patterns.
The English summary is being prepared. Showing the original description.
Evaluate code review feedback against the actual code, supported environments, and existing behavior. Clarify uncertain requests, respond with technical evidence, and implement valid changes one at a time with tests for each fix.
Assign independent bugs or test failures to separate agents that work at the same time. Define each agent’s scope and expected report, then check for conflicting changes and run the full test suite before integrating fixes.
Prepare a separate workspace for feature development using platform tools or git worktree, which gives a branch its own working directory. It checks existing isolation, prepares dependencies, and runs tests before implementation begins.
Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.