Overpowers

Plugin overpowers in Daniiislo/overpowers-kit. Commands read from the repo's manifest — 27 days ago.

Skills (16)

• brainstorming

  Use before new or materially changed product behavior when intent, scope, UX, architecture, or acceptance decisions remain unresolved.

• diagnosing-overpowers

  Use when the Overpowers workflow is slow, repetitive, contradictory, unexpectedly expensive, ignores an approved plan, or applies the wrong verification depth.

• dispatching-parallel-agents

  Use when two or more bounded tasks can proceed independently without shared writes, sequential decisions, or conflicting resources.

• executing-plans

  Use when executing an approved plan directly or resuming planned work in a session.

• finishing-a-development-branch

  Use when implementation reaches an integration checkpoint and needs final review, commit, PR, merge, or cleanup.

• personal-project-team

  Use for non-trivial software planning, implementation, testing, review, or delivery, or when updating the owner's reusable team and model-allocation preferences.

• receiving-code-review

  Use when evaluating review or test findings before deciding whether and how to change the implementation.

• requesting-code-review

  Use when a coherent task or batch is ready for independent verification, or before integration that requires review.

• subagent-driven-development

  Use when executing approved implementation work with delegated agents in the current session.

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• test-driven-development

  Use when implementing new logic, changing behavior, fixing a regression, or refactoring behavior that needs executable protection.

• using-git-worktrees

  Use when work needs isolation from the current checkout, parallel tasks need separate writable state, or repository policy requires a worktree.

• using-overpowers

  Use when starting work to select only the skills and workflow depth that materially help the current request.

• verification-before-completion

  Use before claiming work is complete, fixed, tested, or ready to integrate, and before commit, PR, merge, or release decisions.

• writing-plans

  Use when approved requirements need ordered implementation tasks that another agent, including a smaller model, can execute reliably.

• writing-skills

  Use when creating, changing, validating, or publishing reusable agent skills or this personal workflow plugin.

Similar plugins