openclaw-superpowers-port

Use when a major project step has been completed and needs review against the original plan and coding standards. Provides the Senior Code Reviewer persona for structured 6-phase review: plan alignment, code quality, architecture, documentation, issue categorization, and communication.

Use when you need to trigger brainstorm, write-plan, or execute-plan workflows via short command shortcuts. These are thin dispatchers that invoke the corresponding sp- skills.

Use when creating new skills, editing existing skills, or verifying skills work before deployment. Apply TDD cycle: baseline test first, write skill second, refactor to close loopholes.

Use when completing tasks, implementing major features, or before merging. Dispatches a code-reviewer session to catch issues before they cascade. Review early, review often.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Decision framework for when and how to dispatch parallel sub-agent sessions for faster resolution.

Use when implementation is complete and all tests pass, to decide how to integrate the work. Guides branch completion by presenting 4 structured options: merge locally, push and create a PR, keep as-is, or discard.

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.

Gate skill: run before claiming any work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.

Executes implementation plans by dispatching a fresh subagent per task with two-stage review after each (spec compliance, then code quality). Use when executing a plan with independent tasks in the current session.

4-phase root cause debugging process. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

Enforces strict Red-Green-Refactor TDD discipline. Use when implementing any feature or bugfix, before writing implementation code.

Creates isolated git worktrees with smart directory selection and safety verification. Use when starting feature work that needs isolation from the current workspace or before executing implementation plans.

Converts approved designs into comprehensive, bite-sized implementation plans. Use when you have a spec or requirements for a multi-step task, before touching code.

Batch plan execution with human review checkpoints — use when you have a written implementation plan to execute. Loads the plan, reviews it critically, executes tasks in batches of 3, and reports for review between batches.

Socratic design refinement skill — use before any creative work (creating features, building components, adding functionality, modifying behavior). Explores user intent, requirements, and design through collaborative dialogue before any implementation begins.

Bootstrap/router skill — establishes how to discover and invoke OpenClaw superpowers skills, requiring skill invocation before ANY response including clarifying questions. Use when starting any conversation or task.