roman01la
16 verified skills608 total stars
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development38
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.
development38
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
development38
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
development38
find-bugs
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
development38
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
development38
using-superpowers
Use when starting any conversation - routes work through the correct worker agents before any task action, requiring explicit worker selection and visible compliance
testing38
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development38
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
testing38
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing38
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
testing38
skills/interview
Interview user in-depth to create a detailed spec
data-ai38
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
development38
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
development38
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development38
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-ai38