schlenks
44 verified skills56 total stars
subagent-driven-development
Use when user says "execute epic [id]" or when executing beads epics with parallel subagents in the current session
development2
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
tools2
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development2
plan2beads
Use when converting a Superpowers-BD implementation plan or Shortcut story into a beads epic with dependency-aware child tasks
tools2
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development2
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
tools2
ad-hoc-code-review
Use when the user asks for /cr-style review of local changes, commits, a branch diff, or a GitHub PR outside subagent-driven development
development2
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing2
ad-hoc-code-review
Use when the user asks for /cr-style review of local changes, commits, a branch diff, or a GitHub PR outside subagent-driven development
development2
plan2beads
Use when converting a Superpowers-BD implementation plan or Shortcut story into a beads epic with dependency-aware child tasks
tools2
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing2
subagent-driven-development
Use when user says "execute epic [id]" or when executing beads epics with parallel subagents in the current session
development2
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-ai1
rule-of-five-plans
Use when writing 50+ lines of plans, design docs, skill documents, or process documentation - apply 5 focused passes (Draft, Feasibility, Completeness, Risk, Optimality) to catch issues single-shot generation misses
documentation1
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
tools1
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development1
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
testing1
rule-of-five-tests
Use when writing 50+ lines of test code, adding test suites, or before claiming test work complete - apply 5 focused passes (Draft, Coverage, Independence, Speed, Maintainability) to catch issues single-shot generation misses
development1
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development1
epic-verifier
Use when all implementation tasks in an epic are closed, before calling finishing-a-development-branch
development1
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
testing1
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development1
brainstorming
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
development1
beads
Use when working with the beads (bd) CLI for issue tracking, managing epics and tasks, handling dependencies, or starting/ending coding sessions with persistent work tracking
tools1
multi-review-aggregation
Use when dispatching code reviews for tiers with N greater than 1 (max-20x, max-5x) in subagent-driven development, or manually for critical changes over 200 lines or security-sensitive code
development1
finishing-a-development-branch
Use when ALL tasks in an epic or branch are closed and you are ready to integrate the entire body of work - never after individual task completions, never mid-epic
development1
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
development1
rule-of-five-code
Use when writing 50+ lines of code, implementing features, refactoring, or before claiming code work complete - apply 5 focused passes (Draft, Correctness, Clarity, Edge Cases, Excellence) to catch issues single-shot generation misses
development1
rule-of-five-tests
Use when writing 50+ lines of test code, adding test suites, or before claiming test work complete - apply 5 focused passes (Draft, Coverage, Independence, Speed, Maintainability) to catch issues single-shot generation misses
development1
rule-of-five-plans
Use when writing 50+ lines of plans, design docs, skill documents, or process documentation - apply 5 focused passes (Draft, Feasibility, Completeness, Risk, Optimality) to catch issues single-shot generation misses
documentation1
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-ai1
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
development1
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
testing1
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
tools1
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
testing1
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development1
beads
Use when working with the beads (bd) CLI for issue tracking, managing epics and tasks, handling dependencies, or starting/ending coding sessions with persistent work tracking
tools1
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
development1
brainstorming
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
development1
finishing-a-development-branch
Use when ALL tasks in an epic or branch are closed and you are ready to integrate the entire body of work - never after individual task completions, never mid-epic
development1
epic-verifier
Use when all implementation tasks in an epic are closed, before calling finishing-a-development-branch
development1
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
development1
rule-of-five-code
Use when writing 50+ lines of code, implementing features, refactoring, or before claiming code work complete - apply 5 focused passes (Draft, Correctness, Clarity, Edge Cases, Excellence) to catch issues single-shot generation misses
development1
multi-review-aggregation
Use when dispatching code reviews for tiers with N greater than 1 (max-20x, max-5x) in subagent-driven development, or manually for critical changes over 200 lines or security-sensitive code
development1