implement

Automate TDD feature implementation from tasks.json with stack-agnostic commands.

89|32|Updated May 28, 2026

Search Tags:#code quality #test automation #TDD #feature implementation #stack-agnostic

Ready to run

npx skills add https://github.com/genkovich/sdd --skill implement-genkovich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/genkovich/sdd/tree/main/skills/implement
Command: npx skills add https://github.com/genkovich/sdd --skill implement-genkovich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the implementation of features using Test-Driven Development (TDD), reducing manual effort and ensuring code quality.

Core Features & Use Cases

Test-Driven Development: Writes a failing test first, then makes it pass, refactors, and commits per task.
Stack-Agnostic: Detects and uses the appropriate test, lint, and vet commands for the repository's setup.
Use Case: For a feature with complex requirements, use this Skill to automate the process of writing tests, implementing code, and ensuring code quality through linting and type checking.

Quick Start

Implement a feature by running the command: /sdd:implement <feature-slug>

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate TDD feature implementation from a task definition?▼

You can automate TDD feature implementation by defining requirements in a tasks.json file and executing the implement command, which automatically writes failing tests, implements code to pass them, refactors, and commits per task.

What is stack-agnostic test automation and how does it detect commands?▼

Stack-agnostic test automation detects and executes the appropriate test, lint, and vet commands dynamically based on the repository's setup, allowing the TDD workflow to function across different tech stacks without manual configuration.

Do I need specific test, lint, and vet tools configured to use automated TDD?▼

Yes, automated TDD requires appropriate test, lint, and vet tools configured in your repository, as the stack-agnostic command detection relies on finding these existing tools to validate code quality during the workflow.

Can I use parallelization and team-based workflows for feature implementation?▼

Yes, feature implementation supports parallelization and team-based workflows, allowing multiple tasks from the tasks.json definition to be processed concurrently to accelerate development.

What's the best way to ensure code quality when implementing complex features?▼

The best way to ensure code quality for complex features is using TDD automation, which enforces writing failing tests first, implementing passing code, refactoring, and running lint and type checks per task.

Why does TDD automation require a tasks.json definition file?▼

TDD automation requires a tasks.json definition file because it serves as the structured input that defines the specific feature requirements, enabling the automated workflow to systematically process each task through the test, implement, refactor, and commit cycle.