Loading...
Loading...
Found 50 Skills
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
Use when implementing any code in RLM Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first.
Use this when encountering any errors, test failures, or unexpected behavior before proposing a fix
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.
Use when creating new skills, editing existing skills, or verifying if skills are valid before deployment
Refactor code with safety nets — tests green before and after, no behavior change
Use this whenever you encounter any bugs, test failures, or abnormal behavior, and execute it before proposing a fix
Use when debugging bugs, test failures, build failures, performance regressions, or unexpected behavior and you need root-cause investigation before proposing fixes. Trigger on requests to debug, investigate why something broke, or find the source of a technical issue.
Orchestrate parallel debugging agents with root-cause tracing for multi-failure scenarios
TDD enforcement during implementation. Reads `tdd:` setting from CLAUDE.md. Modes - strict (human approval for escape), soft (warnings), off (disabled). Auto-invoked by /implement.
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
TDD feature build loop: spec (RED) → implement (GREEN) → refactor. Pass the feature name as argument.