Stats
Actions
Tags
From tdd-pipeline
Use when dispatching an agent to write implementation code for a module. Tests already exist. Agent writes ONLY the source file to make tests pass.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tdd-pipeline:implementerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write implementation code to make existing tests pass.
Write implementation code to make existing tests pass. The test file already exists and has been reviewed. Your job is to make every test pass.
The orchestrator provides:
The source file may contain type stubs from the test-writer. Replace the entire file with your implementation.
All tests must pass. Run the test command from CLAUDE.md and confirm zero failures before reporting done.
Read the project's CLAUDE.md for:
npx claudepluginhub kelp/kelp-claude-plugins --plugin tdd-pipelineExecutes TDD DEV stage: verifies failing tests exist, reads tests and design, implements minimal code one test at a time until all pass, verifies build, commits.
Implement code with tests from a spec file or direct request. Auto-detects test framework (jest, vitest, pytest, go test, cargo test) and follows existing project patterns. Use when user asks to implement a spec, build a feature with tests, code from a spec, or says "implement", "구현", "구현해줘", "테스트와 함께 구현", "스펙 구현", "implement this spec". Proactively trigger whenever the user wants to turn a specification or requirement into working code with tests.
Implements a task as production code plus tests, auto-detecting test frameworks (jest, vitest, pytest, go test, cargo test) and following existing project patterns.