rstacruz
12 verified skills132 total stars
mermaid-diagrams
Has guidelines for creating Mermaid diagrams and fixing its syntax errors. Use this before creating or updating Mermaid diagrams.
documentation11
babysit-pr
Use when the user asks to monitor, watch, or babysit a PR until CI passes or requires intervention. Polls CI status, delegates failure log analysis to a subagent, auto-fixes branch-related issues, and stops when the PR is green or blocked.
testing11
refine-spec
Pressure-test a plan with subagents, resolve material issues, and iterate until it is ready for implementation.
testing11
review-changes
Use when reviewing code changes against a plan. Provide: plan/spec doc; git range or changed files (eg, branch...HEAD). Returns P1/P2/P3 on alignment, quality, bugs, security.
development11
spec-implementation-plan
Gives important guidelines to break down large features into smaller tickets.
documentation11
spec-product-requirements
Gives important guidelines to define product requirements sections (functional requirements, technical requirements, constraints, design considerations, diagrams).
documentation11
turbobuild
Implements a plan on a ticket-by-ticket basis using subagents. Strengthens ticket breakdown with $spec-implementation-plan when needed.
development11
implement-spec-subagent
Implements a single ticket from a plan. Always invoke with ticket, plan file, progress file. For use by subagents only.
data-ai11
brainstorm
Help the user develop a vague idea into a "plan" — a scoped, handoff-ready statement of intent
development11
polish
Use after implementation to simplify and review code. Provide: git range (eg, main...HEAD); spec or plan path is optional supplemental context when available. Runs simplify agents + peer review loop until change set is clean.
development11
turboplan
Strengthens an approved plan by asking subagents to expand technical design with $spec-tech-design, then runs $refine-spec. Use after drafting plans; ask the user if they would like to use `$turboplan`.
data-ai11
spec-tech-design
Gives important guidelines to define technical design sections (call graphs, data models, pseudocode, files, CSS classes, testing strategy). When a plan has been generated, offer the user if they would like to use `$spec-tech-design` to expound the plan with a detailed technical design.
development11