golang-workflow

golang-workflow

TDD-first parallel agents with intelligent failure triage for Claude Code

Why golang-workflow?

• 9 specialized agents that explore, design, implement, test, review, and optimize your Go code — each with a focused role and the right model for the job
• Test-implementation isolation ensures unbiased test coverage — the test writer never sees your implementation code, and the implementer never sees the test code
• Intelligent failure triage classifies each test failure as a code bug, test bug, or contract mismatch, then re-runs only the agent that needs fixing
• Dual-mode orchestration — parallel mode for speed, TDD mode (--tdd) for strict red-green-refactor discipline
• Automated quality gates with race detection, coverage thresholds, static analysis, and linting — zero configuration required
• 40 skill files encoding idiomatic Go patterns for concurrency, error handling, interfaces, nil safety, testing, and linting

Quick Start

Installation

/install-plugin <marketplace-url>

Usage

Run a full parallel implementation workflow:

/implement Add a rate-limited HTTP client with exponential backoff

Run with strict TDD (tests first, verified to fail, then implementation):

/implement --tdd Add a concurrent-safe LRU cache with TTL expiration

Lightweight bug fix or refactor:

/patch Fix the nil pointer dereference in ParseConfig when input is empty

The plugin orchestrates the rest — exploration, design, implementation, testing, review, and optimization happen automatically across specialized agents.

Features

Test-Implementation Isolation

Traditional AI coding writes tests after seeing the implementation, creating tests that mirror the code rather than verify the contract. golang-workflow solves this:

The test writer works from the architect's specification — scenario tables, error conditions, edge cases, fuzz targets — without any knowledge of how the code is structured. The implementer knows what behaviors will be tested but not how the tests assert them. This separation produces tests that genuinely verify the contract rather than parroting the implementation.

flowchart TD
    W1[Wave 1: Parallel Exploration]
    E[Explorer]
    A[Architect]
    R[Researcher]
    W2a[Wave 2a: Parallel Creation]
    I[Implementer]
    TW[Test Writer]
    W2a5[Wave 2a.5: Compilation Check]
    W2b[Wave 2b: Quality Gate]
    TR[Test Runner]
    RV[Reviewer]
    T{Triage}
    W3[Wave 3: Final Review]
    TR2[Test Runner]
    RV2[Reviewer]
    O[Optimizer]
    W4[Wave 4: Verification]