rodrigopaitach
UserSpec-driven development for coding agents where every claim carries a file:line citation and verifiers re-run the search. For developers and non-programmers alike. Derived from Superpowers (MIT).
Categories
Indexed Skills (15)
brainstorming
Explores user intent, requirements and design before implementation, and produces an approved spec. Required before any creative work - creating features, building components, adding functionality, or modifying behavior.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plans
Executes a written implementation plan inline, in the current session, with both end-of-branch gates. Use when a written implementation plan is ready to execute.
final-branch-audit
Use when all plan tasks are done and before finishing a development branch - traces every spec criterion to the plan's tasks, then audits every task one by one and proves each acceptance criterion with located evidence
finishing-a-development-branch
Decides how to integrate finished work - merge locally, open a pull request, or keep the branch. Use when implementation is complete and all tests pass.
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
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks 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 any feature or bugfix, before writing implementation code
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
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
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
writing-plans
Turns a spec or requirements into a task-by-task implementation plan. Use when a multi-step task has a spec or requirements, before touching code.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.