Loading...
Loading...
Found 146 Skills
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Writes failing tests first for test-driven development and hands off a strict implementation contract that requires agents to make those tests pass without weakening the tests. Use when users ask for test-first workflows, RED/GREEN cycles, or behavior-gating tasks with automated tests.
Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, asks for test-first development, or wants stronger integration tests.
Turn a spec or requirements into a bite-sized implementation plan. File-structure-first (deep modules), embedded grill to stress-test, no forced sub-skill chains. Use when you have a spec or clear requirements and are ready to plan execution.
Use when implementing any code in recursive-mode Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first. Trigger phrases: "implement this", "add feature", "fix bug", "write a failing test", "TDD".
Test-driven development with Kent Beck's canonical 5-step workflow: Test List, Write Test, Make Pass, Refactor, Repeat. Strict vertical-slice cycles with automatic project detection. Use when the user asks to "write tests first", "use TDD", "red-green-refactor", "test-driven development", "build a feature with TDD", "fix a bug with TDD", wants test-first development for any language or framework, or mentions "tracer bullet" or "vertical slice".
Use when writing any code - enforces test-driven development discipline with RED-GREEN-REFACTOR cycle, fires during any coding task
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
You MUST use this when an approved design or settled requirements need a detailed multi-step implementation plan before code changes begin.