ultrapowers

This skill should be used when facing 2+ independent tasks that can be worked on without shared state, or when coordinating subagent-driven implementation of a plan. Covers parallel dispatch and sequential task orchestration.

This skill should be used when the user asks to 'brainstorm', 'design this', 'think through', 'plan this out', 'what should we build', 'how should this work', 'let's think about', 'explore approaches', or 'before we start'. Also appropriate when beginning tasks with genuine ambiguity: multiple reasonable approaches, unclear requirements, or cross-cutting changes spanning multiple subsystems.

This skill should be used when receiving code review feedback, requesting review before merging, or when completing a major feature. Covers both giving and receiving reviews with technical rigor.

This skill should be used when encountering any bug, test failure, or unexpected behavior — before proposing fixes. Also appropriate when a previous fix attempt didn't work, when under time pressure to fix something, or when thinking 'just try changing X'.

This skill should be used when writing implementation plans for multi-step tasks, or when executing an existing written plan. Appropriate after a design is approved and before touching code, or when picking up a plan file to implement.

This skill should be used when implementing any feature or bugfix, before writing implementation code. Also when fixing a bug without a regression test, or when tempted to 'write tests after'.

This skill should be used when about to claim work is complete, fixed, or passing — before committing, creating PRs, or telling the user 'done'. Requires running verification commands and reading output before making success claims.