Loading...
Loading...
Found 120 Skills
Implement features from a validated RootSpec specification — test-driven and autonomous. Use this when a user wants to build, code, or implement features from their spec, or when they want to make failing tests pass.
Guide users through TDD and TCRDD (Test && Commit || Revert + Test Driven Development). Use this skill whenever a user mentions TDD, test-driven development, writing tests before code, red-green-refactor cycles, or unit testing workflows. Also trigger when a user asks about TCRDD, TCR, "test commit revert", "git gamble", or wants a strict TDD workflow with automatic commits and reverts. Trigger when the user asks to implement a feature, fix a bug, or write a class/function and mentions tests, TDD, or "test first". If the user shares code and asks for a review with any testing angle, consult this skill.
TDD London School workflow -- mock-first, outside-in test development
Use this for development.
Guiding principles for writing clear, concise, human readable and maintainable Python code.
TDD workflow for migrations - orchestrate agents, zero main context growth
Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.
Unified TDD workflow skill combining 6-phase TDD planning with Red-Green-Refactor task chain generation, and 4-phase TDD verification with compliance reporting. Triggers on "workflow-tdd-plan", "workflow-tdd-verify".
Execute and implement approved specification proposals in sequence using a test-and-validation-first approach. It is used for implementing changes, applying proposals, executing specification tasks, or building according to approved plans. Trigger words include "speckit-implement", "speckit-develop", "develop", "implement", "realize proposal", "apply change", "execute specification", "complete tasks in order", "build feature", "start implementation".
Développement piloté par les tests avec boucle red-green-refactor. À utiliser quand l'utilisateur veut construire des fonctionnalités ou corriger des bugs en TDD, mentionne « red-green-refactor », veut des tests d'intégration ou demande du développement test-first.
Write the minimal production code needed to make all existing failing tests pass. No extra features, no test modifications, no refactoring. Use after tests are written and confirmed failing.
Refactor code with safety nets — tests green before and after, no behavior change