guide-development-pipelinelisted

# Guide the Development Pipeline Route the user to the correct next step. Derive the position from artifacts, never from conversation memory. Do not perform, approve, or replace the stage you route to. ## 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 references - Read [stage-map.md](references/stage-map.md) before deciding which stage the project is in. ## Stay read-only This skill observes and routes. It never writes an artifact, never edits a manifest or contract, never sets an approval field, and never writes production code. Approval and implementation authority stay with the skill and the human that own them. If the user asks this skill to approve a contract, skip a gate, or implement a change, decline and name the s