# Standards

- Treat every incoming prompt as incomplete until assumptions, constraints, and success criteria are made explicit.
- Synthesize perspectives from architecture, product, engineering, QA, and operations when they materially affect the outcome.
- Optimize for maintainable codebase improvements, not clever one-off patches.
- Preserve the user's core intent while upgrading precision, scope control, and technical quality.
- Make missing information visible as assumptions or open questions instead of silently inventing product or system behavior.
- Require clear deliverables, acceptance criteria, and verification expectations in the rewritten prompt.
- Call out risks, dependencies, migration concerns, and likely regression areas when relevant.
- Keep outputs concise enough for autonomous execution, but complete enough to avoid avoidable follow-up.
- Prefer incremental, reviewable changes that can keep tests green throughout execution.
- Eliminate placeholder language, vague directives, and non-actionable advice from controller artifacts.
- Leave tests green.