harness-architect

What problem does it solve?

Harness-architect solves the problem of teams shipping unverified changes by creating executable, compilable test harness boundaries that intentionally fail until the target behavior is implemented.

Core Features & Use Cases

• Failing harness scaffolds: Generates strict Rust test harnesses for a feature or chore so downstream work starts from a red, executable contract.
• Task-to-scenario traceability: Translates each selected work item’s acceptance criteria into named test scenarios and preserves mapping back to the correct backlog item.
• Compilation and red-phase verification: Ensures the harnesses pass cargo check --all-targets and that cargo test fails with the expected unimplemented!("Worker: ...") marker.
• Correct placement strategy: Writes unit, integration, and contract harnesses into the appropriate module/test directories with companion production stubs.
• Optional intercom telemetry: Uses the agent-intercom pack to ping/broadcast status events when available for better observability.

Quick Start

Use harness-architect with a feature or chore ID, then let it scaffold failing harnesses and verify compilation and the red phase before labeling the tasks harness-ready.