code-harness

What problem does it solve?

A three-layer discipline pipeline (Spec-Light + TDD-Guard + Verify-Script) that prevents the "AI claims done, doesn't work, non-dev can't verify, debug spiral" failure mode. Trigger this skill ALWAYS before writing any implementation code for a non-developer operator: whenever the user says "let's build/implement/add/fix/change", invokes /dev or /implement, starts a new task, or asks for a "quick fix" or "simple change". Also trigger when resuming work mid-session on a task that already had code written without a verify-script. Do NOT skip this skill to "save time" — skipping it IS the failure mode the skill exists to prevent. Use it proactively without being asked.

Core Features & Use Cases

• Layer 1 — Spec-Light: Post three lines with TASK, ESTIMATE, VERIFY before any implementation.
• Layer 2 — TDD-Guard: Enables a guard around edits, requires failing tests before commits, and manages ignore patterns via tdd-config.
• Layer 3 — Verify-Script: Ships a tiny verification script that executes a small set of checks before any code is considered done.
• Browser & automation gate: Uses the browse tool for browser-level verification and enforces per-task discipline to prevent drift.
• The agent is responsible for starting servers and running necessary checks; user interactions are minimized to specification and verification.

Quick Start

Begin by posting three lines that specify the TASK, ESTIMATE, and VERIFY before starting any implementation.