Superpowers Neo

Plugin superpowers-neo in LingquLab/harness. Commands read from the repo's manifest — 2 days ago.

Skills (11)

• superpowers-neo-code-simplification

  Use after implementing or modifying code or user-facing documentation and before final review or Git delivery, or when asked to simplify, clean up, or reduce complexity without changing behavior

• superpowers-neo-designing-complex-changes

  Use when a requested change is complex, has key ambiguity, spans components, has cross-component effects, or requires an architectural decision.

• superpowers-neo-executing-plans

  Use when an in-scope implementation plan is ready for execution, especially for multi-step work that may benefit from scoped delegation or coordinated parallelism

• superpowers-neo-git-delivery

  Use after completing feature or bug-fix work in a Git repository; for explicit or general Git delivery requests; or when manually invoked to authorize current-task branch selection, a scoped commit when needed, normal push, and pull request creation

• superpowers-neo-handling-code-review-feedback

  Use when evaluating or implementing code review feedback, including comments that appear straightforward, ambiguous, disputed, technically significant, potentially incorrect, or scope-expanding

• superpowers-neo-requesting-code-review

  Use when a code change is broad, cross-module, public-interface, concurrent, security-sensitive, data-consistency-sensitive, or otherwise risky enough to benefit from independent review

• superpowers-neo-systematic-debugging

  Use when a bug, test failure, build issue, performance problem, or unexpected behavior has an uncertain cause, conflicting evidence, or a failed attempted fix.

• superpowers-neo-using-git-worktrees

  Use when a user requests isolation, parallel writes may conflict, the current Git workspace is unsafe, or staged, unstaged, or untracked files may belong to another task

• superpowers-neo-validation-strategy

  Use when deciding what tests or other evidence a code, configuration, or documentation change needs, especially for bug fixes, risky behavior, unavailable hardware, or costly automation.

• superpowers-neo-verification-before-completion

  Use when work is about to be described as complete, fixed, resolved, passing, or ready, especially after final edits or when validation is incomplete or mixed

• superpowers-neo-writing-plans

  Use when execution is multi-step, high-risk, cross-module, likely to span sessions, or intended for handoff to another agent.

Similar plugins