address-merge-conflict
Gives guidelines for addressing a Git merge conflict with user intervention. Do not invoke unless user asks.
explain-code
>
high-density-writing-style
>
mermaid-diagrams
>
plan-mode
Guidelines for Plan Mode. Use for simple tasks only
analyse-pr
Analyse a pull request
coding-practices
>
ralph-execute-via-subagent
A "ralph loop" iterates through a plan in a ticket-by-ticket basis. Use this when use *specifically* asks for a "ralph loop".
execute-plan
Execute a plan
plan-refine
Refine a plan with subagents
refine-implementation
TBD
refine-tests
Guidelines for identifying redundant tests, coverage gaps, opportunities for imp=oving tests
review-changes
> Reviews code changes. When using this skill, provide: plan document (eg, PRD, TDD); changed file and locations; git range (if available, eg, "branch...HEAD"). Return recommendations (P1 critical, P2, P3).
spec-implementation-plan
Gives important guidelines to break down large features into smaller tickets. Companion to spec-mode.
spec-mode
Guide LLM through interactive specification creation workflow — research codebase, gather requirements via question tool, draft product requirements, technical design, and implementation tickets iteratively with user feedback
spec-product-requirements
Gives important guidelines to define product requirements sections (functional requirements, technical requirements, constraints, design considerations, diagrams). Companion to spec-mode.
spec-tech-design
Gives important guidelines to define technical design sections (call graphs, data models, pseudocode, files, CSS classes, testing strategy). Companion to spec-mode skill.
testing-practices
>