Harness Engineering

Evolve an existing repository toward Harness Engineering without pretending it must be rebuilt as a blank template. Prefer repo-local knowledge, predictable structure, and executable checks over aspirational documentation and hidden context.

Workflow

1. Audit the current repo

• Read AGENTS.md and the top-level docs under docs/.
• Identify missing source-of-truth artifacts, dead references, placeholder CI, and stack-specific assumptions.
• Confirm whether the repo is a real app, a governance layer, or a starter template.
• Preserve existing product and runtime structure where possible. Do not force a greenfield layout onto a mature codebase.

2. Establish the minimum repo-local artifacts