Harness Improvement Loop

Use this skill when

• the same class of issue keeps recurring
• generated work often needs the same correction
• verification is repeatedly weak
• handoffs are not good enough
• traces are insufficient for diagnosis

Goals

• improve the harness instead of only fixing local artefacts
• reduce repeated waste
• strengthen planning, generation, evaluation, and handoff quality

Process

1. Collect evidence from failures, traces, or weak reviews.
2. Classify the recurring pattern.
3. Identify the likely harness-level cause.
4. Propose a small high-leverage improvement.
5. Define rollout steps.
6. Define how to validate the improvement.

Output contract

Return:

• recurring pattern
• evidence
• likely harness cause
• improvement proposal
• rollout plan
• success criteria