Menú
SkillsMP ha recopilado 15 skills de obra/superpowers. Abre una skill para revisar su origen y sus detalles.
Mostrando 15 de 15 skills recopiladas.
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.
Idioma del texto original: inglés
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug…
Idioma del texto original: inglés
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Idioma del texto original: inglés
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Idioma del texto original: inglés
Use when executing implementation plans with independent tasks in the current session
Idioma del texto original: inglés
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Idioma del texto original: inglés
Use when implementing any feature or bugfix, before writing implementation code
Idioma del texto original: inglés
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Idioma del texto original: inglés
Use when you have a spec or requirements for a multi-step task, before touching code
Idioma del texto original: inglés
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Idioma del texto original: inglés
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Idioma del texto original: inglés
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Idioma del texto original: inglés
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
Idioma del texto original: inglés
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
Idioma del texto original: inglés
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
Idioma del texto original: inglés