Finish completed development work by checking the full test suite and presenting integration choices: merge locally, create a Pull Request, or keep the branch. It carries out the selected path and handles workspace cleanup accordingly.
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.
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.
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.
Carry out an existing implementation plan in one session, task by task. Verify each step with tests, record progress and decisions in a file, and finish with a review of all changes on the branch.
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.
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.
Requests a code review from a separate agent after implementation or before merging. It provides the change summary, requirements, and commit range, then guides follow-up work according to the severity of the findings.
Investigate bugs, failing tests, and unexpected behavior using reproduction steps, logs, and recent changes. Follow a structured process to identify the root cause, test a specific explanation, and verify the resulting fix.
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.
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.
Guides feature development and bug fixes by writing tests before implementation. It confirms each test fails for the expected reason, adds only enough code to pass, and checks the full test suite before completion.
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.
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.
Carry out an implementation plan by assigning each task to a separate agent, then reviewing specification compliance and code quality. Keep progress in files and review the complete set of changes after all tasks are finished.
Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"
The English summary is being prepared. Showing the original description.
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
The English summary is being prepared. Showing the original description.
Dispatch to the right problem-solving technique based on how you're stuck
The English summary is being prepared. Showing the original description.
TDD for process documentation - test with subagents before writing, iterate until bulletproof
The English summary is being prepared. Showing the original description.
Understand how ideas evolved over time to find old solutions for new problems and avoid repeating past failures
The English summary is being prepared. Showing the original description.
Write the test first, watch it fail, write minimal code to pass
The English summary is being prepared. Showing the original description.
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
The English summary is being prepared. Showing the original description.
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
The English summary is being prepared. Showing the original description.
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)