implement
SolidTDD implementation - make failing tests pass
AI & Automation 15 stars
3 forks Updated today MIT
Install
Quality Score: 82/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# 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...
Details
- Author
- jmylchreest
- Repository
- jmylchreest/aide
- Created
- 5 months ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Solid
tdd
Test-driven development — write a failing test that names the behavior, watch it fail, implement the minimum to make it pass, then refactor with tests green. Works for new features, bug fixes, and behavior changes. Use when the user says "tdd", "test-first", "write tests first", or wants a change built test-first.
73 Updated today
genai-io AI & Automation Listed
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
8 Updated today
dork-labs AI & Automation Solid
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
9 Updated today
JustMichael-80