Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
executing-plans
Use to execute bd tasks iteratively - executes one task, reviews learnings, creates/refines next task, then STOPS for user review before continuing
withzombies/hyperpowers 72
-
verification-before-completion
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
withzombies/hyperpowers 72
-
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
withzombies/hyperpowers 72
-
dispatching-parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple agents to investigate and fix independent problems concurrently
withzombies/hyperpowers 72
-
finishing-a-development-branch
Use when implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice
withzombies/hyperpowers 72
-
testing-anti-patterns
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
withzombies/hyperpowers 72
-
managing-bd-tasks
Use for advanced bd operations - splitting tasks mid-flight, merging duplicates, changing dependencies, archiving epics, querying metrics, cross-epic dependencies
withzombies/hyperpowers 72
-
hyperpowers-agents
Use when you want to spawn a specialized subagent using the standard Hyperpowers agent prompts (test-runner, code-reviewer, codebase-investigator, internet-researcher, test-effectiveness-analyst).
withzombies/hyperpowers 72
-
refactoring-safely
Use when refactoring code - test-preserving transformations in small steps, running tests between each change
withzombies/hyperpowers 72
-
root-cause-tracing
Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom
withzombies/hyperpowers 72
-
analyzing-test-effectiveness
Use to audit test quality with Google Fellow SRE scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases. Creates bd epic with tasks for improvements, then runs SRE task refinement on each.
withzombies/hyperpowers 72
-
brainstorming
Use when creating or developing anything, before writing code - refines rough ideas into bd epics with immutable requirements
withzombies/hyperpowers 72
-
test-driven-development
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
withzombies/hyperpowers 72
-
sre-task-refinement
Use when you have to refine subtasks into actionable plans ensuring that all corner cases are handled and we understand all the requirements.
withzombies/hyperpowers 72
-
refactoring-diagnosis
Use when identifying bad code/design and selecting refactor targets - produces a diagnosis report with smells, risks, and refactor vs rewrite decision
withzombies/hyperpowers 72
-
review-implementation
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
withzombies/hyperpowers 72
-
debugging-with-tools
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
withzombies/hyperpowers 72
-
writing-plans
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
withzombies/hyperpowers 72
-
fixing-bugs
Use when encountering a bug - complete workflow from discovery through debugging, bd issue, test-driven fix, verification, and closure
withzombies/hyperpowers 72
-
building-hooks
Use when creating Claude Code hooks - covers hook patterns, composition, testing, progressive enhancement from simple to advanced
withzombies/hyperpowers 72
-
using-hyper
Use when starting any conversation - establishes mandatory workflows for finding and using skills
withzombies/hyperpowers 72
-
executing-plans
Use to execute bd tasks iteratively - executes one task, reviews learnings, creates/refines next task, then STOPS for user review before continuing
withzombies/hyperpowers 72
-
verification-before-completion
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
withzombies/hyperpowers 72
-
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
withzombies/hyperpowers 72