pcvelz
16 verified skills13,632 total stars
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development1,047
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
tools925
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
development925
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
development925
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing925
checking-gates
Use when picking up a user-gate task OR when a hook demands re-validation. Runs the "do I know HOW?" self-check; if the HOW is clear, executes the verification and posts evidence; if not, hands off to specifying-gates. Kept deliberately separate from executing-plans so that without the opt-in hook, the main flow stays untouched.
testing925
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
development925
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development925
specifying-gates
Use when a user-gate task has requiresUserSpecification=true OR the agent's "do I know HOW?" self-check returns no. Locks down verification mechanics through a short AskUserQuestion sequence and writes the answers back into the task's metadata. Does NOT run the verification itself.
testing925
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
tools925
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development710
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
development710
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
testing710
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
testing710
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
data-ai710
receiving-code-review
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
development710