pipeline-implement

Translate architecture designs into working code using TDD-driven RED-GREEN-REFACTOR cycles.

3|1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/I-Onlabs/claude-code-skills --skill pipeline-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-implement
Source: https://github.com/I-Onlabs/claude-code-skills/tree/main/pipeline-implement
Command: npx skills add https://github.com/I-Onlabs/claude-code-skills --skill pipeline-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating architecture-to-code transitions in software projects by enforcing a disciplined, repeatable TDD-driven workflow that reduces defects and accelerates delivery.

Core Features & Use Cases

  • Red-Green-Refactor cycle guidance for implementing features after architecture review.
  • Implementation checklists and coding standards to improve quality and consistency.
  • ADR-aligned workflow with clear next steps and handoffs to testing.

Quick Start

Follow the RED-GREEN-REFACTOR cycle to implement the next feature after reviewing the ADR and acceptance criteria.

Frequently Asked Questions about pipeline-implement

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

FAQPage Schema
How do I implement code from architecture designs using TDD?

To implement code from architecture designs using TDD, follow a structured RED-GREEN-REFACTOR cycle guided by ADRs and acceptance criteria. This enforces test-driven development to translate designs into working code with clear handoffs to testing.

What is the RED-GREEN-REFACTOR cycle in software engineering?

The RED-GREEN-REFACTOR cycle is a test-driven development workflow that structures code implementation. It enforces writing failing tests first, making them pass, and improving code quality to reduce defects and accelerate delivery.

How do I enforce code quality standards during feature implementation?

You can enforce code quality standards during feature implementation by applying coding checklists and ADR-aligned workflows. This structures progress reporting and ensures consistency across design-to-code transitions in your software project.

Can I use this TDD workflow after an architecture review?

Yes, this TDD workflow is specifically designed for the stage after architecture review. It translates ADRs and architecture designs into working code by guiding the implementation of features through disciplined test-driven cycles.

What is the best way to coordinate architecture-to-code transitions?

The best way to coordinate architecture-to-code transitions is by using a disciplined, repeatable TDD-driven pipeline. This approach enforces implementation checklists and coding standards to reduce defects and accelerate software delivery.

When do I need a TDD-driven pipeline for software development?

You need a TDD-driven pipeline when translating architecture designs into working code and aiming to reduce defects. It provides structured progress reporting and enforces coding standards during the implementation phase of software development.