implement

Convert failing stubs into working implementations that pass the test suite.

Updated Aug 23, 2026

Search Tags:#testing #tdd #repositories #software-engineering #implement #incremental

Ready to run

npx skills add https://github.com/sofer/.agents --skill implement-sofer

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert failing or incomplete stubs into fully working implementations that make all tests pass, enabling rapid, confidence-building progress in TDD workflows.

Core Features & Use Cases

Incremental implementation: replace one failing stub at a time with minimal, verifiable code.
Design-aligned: follow project architecture, naming, and error-handling conventions while expanding functionality.
Verification-first: run the test suite to confirm correctness and guard regressions across repositories, services, and controllers.

Quick Start

Start by running the test suite to identify failures, then implement the smallest working solution that makes the failing tests pass.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I turn failing stubs into working code for TDD?▼

To turn failing stubs into working code for TDD, run the test suite to identify failures, then replace each stub incrementally with the minimal working solution that makes the failing tests pass.

What's the best way to implement incremental fixes across repositories, services, and controllers?▼

The best way to implement incremental fixes across repositories, services, and controllers is to replace one failing stub at a time with minimal, verifiable code that aligns with project architecture and passes the test suite.

Can I use this approach to verify code correctness and guard against regressions?▼

Yes, you can use this approach to verify code correctness and guard against regressions. It operates verification-first by running the project's test suite after expanding functionality to confirm all tests pass.

Does implementing stubs this way follow existing project conventions?▼

Yes, implementing stubs this way follows existing project conventions. It is design-aligned, meaning it adheres to your project's architecture, naming, and error-handling conventions while expanding functionality.

Why are my test-driven development stubs still failing after implementation?▼

Your test-driven development stubs may still be failing if the implementation was not minimal or verifiable. You should apply incremental fixes one stub at a time and run the test suite to confirm correctness and guard regressions.

When do I need to replace incomplete stubs with full implementations in a TDD workflow?▼

You need to replace incomplete stubs with full implementations in a TDD workflow when you have failing tests that require working code. This enables rapid, confidence-building progress by converting stubs into complete implementations that pass.