Software Development skills

S

SPARC Methodology

ruvnet

A structured framework for comprehensive software development.

Debug

anthropics

Systematic debugging for effective issue resolution.

Code Review Checklist

sickn33

Ensure thorough code reviews with a systematic approach.

Adversarial Code Reviewer

alirezarezvani

Enhance code quality with critical, multi-perspective reviews.

C

Code Goal Planner

ruvnet

Transform coding tasks into achievable milestones.

S

SPARC Coordinator

ruvnet

Orchestrate systematic software development phases.

Improve Codebase Audit

shadcn

Generate actionable implementation plans for code improvement.

Test-Driven Development

mattpocock

Master the red-green-refactor cycle for effective testing.

S

Subagent-Driven Development

rpamis

Streamline task execution with specialized subagents.

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Refactoring using Extract Methods in Java Language

Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

Turn a vague, intermittent, or environment-specific bug report into a minimal evidence-backed reproduction before proposing a fix.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.