gpt-orchestration-build
GPT Orchestration Build
Use installed GPT Engineer for the shared engineering contract. This wrapper adds findings-driven execution, not a separate model policy. Installation does not resolve a core dependency or register profiles/hooks. If the core is unavailable, preserve the current parent and apply the bounded workflow below directly.
Respect the selected gpt-6-astra, gpt-5.6-sol, gpt-5.6-terra, or gpt-5.6-luna
parent. A fleet is optional. Request useful same-model children explicitly, or select a mixed-model
policy with exact routes and reasons. Never silently substitute an older model or change provider.
Read repository instructions and current Git state; preserve user/concurrent edits. Carry prior authorization within this task. Validate supplied findings against current source, tests and relevant primary documentation. Track ID, root cause, impact, paths, dependencies, owner, acceptance and disposition. Do not restart broad discovery unless the evidence is unusable.