← ClaudeAtlas

implementlisted

TDD implementation - make failing tests pass
jmylchreest/aide · ★ 10 · AI & Automation · score 76
Install: claude install-skill jmylchreest/aide
# Implement Mode **Recommended model tier:** smart (opus) - this skill requires complex reasoning Focused TDD implementation: make failing tests pass with minimal code. ## Purpose This is the DEV stage of the SDLC pipeline. Tests already exist from the TEST stage. Your job is to write the minimal implementation that makes them pass. ## Prerequisites Before starting: - Tests exist and are failing (from TEST stage) - Design/spec is available (from DESIGN stage) - You know which files to create/modify ## Workflow ### Step 1: Verify Tests Exist and Fail ```bash # Run the tests - they MUST fail initially npm test -- path/to/feature.test.ts # or go test ./pkg/feature/... ``` **If tests pass**: The work is already done. Mark complete and move on. **If tests don't exist**: This is wrong - go back to TEST stage. ### Step 2: Read the Tests Understand what the tests expect: - What functions/methods need to exist? - What are the expected inputs and outputs? - What edge cases are covered? ```bash # For large test files, get the structure first mcp__plugin_aide_aide__code_outline file="path/to/feature.test.ts" # Then read specific test sections with offset/limit Read path/to/feature.test.ts offset=<start> limit=<count> # For small test files (<100 lines), reading the full file is fine Read path/to/feature.test.ts ``` When implementing, use `code_outline` on adjacent/related source files to understand their structure before reading them fully. This preserves context for t