run-verified-development-looplisted

# Run a Verified Development Loop Use one manager-controlled state machine. Let models propose changes; let deterministic tools decide whether the code works. ## Respond in the user's language Detect the user's language from their messages and use it for all prose addressed to them: questions, explanations, recommendations, status, and the closing summary. Keep every machine token verbatim — code, commands, file paths, schema field names, stable IDs, and the status or verdict values this skill returns — and convey their meaning in the surrounding prose rather than translating the tokens. If the user's language is unclear, ask once, then continue in the chosen language. Persisted artifacts are contracts, not chat. Keep their template headings, YAML keys, stable IDs, and status tokens exactly as specified so downstream skills and validators keep working. Narrative content inside an artifact may follow the user's language when the user asks for it. ## Load supporting material Read only the references needed for the current run: - Read [roles-and-routing.md](references/roles-and-routing.md) before assigning models or agents. - Read [run-preflight.md](references/run-preflight.md) before entering the state machine. - Read [contracts.md](references/contracts.md) before delegating any work package. - Read [quality-gates.md](references/quality-gates.md) before implementing or verifying changes. - Read [architecture-integration.md](references/architecture-integration.md) when a