denerose
11 verified skills
vom-assess-new-tickets
Uses vom list for the NEW queue (up to ten), then dispatches a fresh subagent per ticket with VOM new-state guidance pasted in the prompt; each subagent claims, triages, and advances via vom CLI. Use when batch-triaging new tickets with isolated review per ticket.
tools
vom-self-review
Review recent work for friction and pain points. Create or update tickets for issues that made the agent's job harder. Focus on project-specific improvements only.
testing
prisma-delegate-migrate
When Prisma migrate must run outside a subagent sandbox — subagent edits schema only and hands off exact commands; host runs bunx prisma and confirms.
data-ai
superpowers-subagents-final-check
Closes the loop after subagent-driven code-quality or spec reviews by reconciling all reviewer feedback with the repo, then creating VOM tickets for valuable work that is still open. Use after a Task/code-reviewer chain, when finishing a multi-task plan, or when the user asks to process review feedback into tickets.
development
vom-new
Guide for creating a new VOM ticket using the vom CLI so tickets are good-quality and workflow-aligned.
tools
vom-plan-review
Reviews, amends, and improves a VOM implementation plan for a ticket in plan-needs-review using only the vom CLI for claims, guidance, comments, and state transitions; edits plan markdown under plans/ only. Use when the user wants a plan approved (moved to plan-approved), wants plan-needs-review handled end-to-end, or invokes plan review with extra notes or constraints in the prompt.
tools
vom-tidy
Move VOM tickets with state done or deleted into tickets/done or tickets/deleted to keep the main list tidy.
data-ai
vom-plan-finder
Lists every VOM ticket in plan-needs-review via the vom CLI, prints Cursor-clickable links to each plan markdown file, and summarizes additions, improvements, and review considerations for the human—without approving plans or advancing workflow. Use when the user wants a plan review queue, "what needs plan review", or an overview of pending implementation plans before approval.
tools
vom-open-plan
Open the implementation plan file for a VOM ticket. Ticket ID can come from the user's request or from current context (e.g. open file under .vom/tickets/, conversation). Use when the user asks to open the implementation plan, when a ticket is in or transitions to plan-needs-review, or when viewing the plan for TKT-XXX.
tools
vom
Guide for continuing work on a VOM ticket - reminds agents to claim and check guidance before starting.
testing
subagent-driven-development
Execute implementation plans with a fresh subagent per task, spec review then code-quality review; includes capture rules for reviewer feedback. Controllers must run superpowers-subagents-final-check before branch closeout. Repo copy with prompt templates in this folder.
development