write-code

Implement minimal code to pass failing tests in a TDD cycle.

Updated Jun 12, 2026

Search Tags:#automation #testing #tdd #refactoring #implementation #pipeline

Ready to run

npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill write-code-ambrovia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-code
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/write-code
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill write-code-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of scope creep and inefficient coding by enforcing a strict Test-Driven Development (TDD) cycle where implementation is limited strictly to what is required to make failing tests pass.

Core Features & Use Cases

TDD Green Phase Execution: Automatically focuses implementation efforts on satisfying existing red tests.
Gate Verification: Ensures that all code changes pass the project's full verify command before completion.
Documentation Sync: Enforces that any behavioral changes are documented in the same commit as the implementation.
Use Case: When a work package has failing tests, use this skill to implement the necessary logic, verify the gate, and ensure all documentation is updated, preventing the introduction of unrequested features.

Quick Start

Invoke the write-code skill to implement the necessary logic for the current work package and verify that all tests pass.

Frequently Asked Questions about write-code

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

FAQPage Schema

How do I implement code to pass failing tests without introducing scope creep?▼

Test-driven development implementation requires writing the minimum code necessary to satisfy failing test cases. The write-code skill executes this TDD green phase, strictly limiting logic to test requirements to prevent unrequested features.

What is the TDD green phase and how does it enforce regression testing?▼

The TDD green phase is the implementation stage where minimum code is written to make failing tests pass. It enforces regression testing by operating within a structured pipeline that requires passing a full verify command before completion.

How do I keep documentation synchronized when implementing new code logic?▼

Documentation synchronization during implementation requires committing behavioral changes alongside the code. This skill enforces documentation parity by ensuring any behavioral modifications are documented in the exact same commit as the implementation.

Can I use automated refactoring within a multi-agent pipeline for test-driven development?▼

Yes, automated refactoring within a multi-agent pipeline supports test-driven development by ensuring code quality and gate verification. The implementation operates within this structured pipeline to maintain system integrity throughout the coding cycle.

Does strict TDD implementation prevent adding features beyond the failing test requirements?▼

Yes, strict TDD implementation prevents scope creep by enforcing a cycle where code is limited strictly to what is required to make failing tests pass. This ensures no unrequested features are introduced during the logic implementation.