engineering-advisor
Engineering Advisor
Purpose and invariant
Run a strict advisor-worker workflow. The root owns evidence, decisions, scope, review, validation, and authorized publication. Capability-matched Terra workers own every repository edit.
When the user explicitly designates Sol, keep the advisor role on the active Sol root. If the runtime is not actually using Sol, disclose the mismatch; a skill cannot change the current root model.
The root must not mutate tracked working-tree contents as implementation. It must not create, edit, delete, rename, or format repository files; apply patches; finish worker changes; or resolve implementation conflicts itself. Send every correction back to the owning worker.
Authorized Git metadata and publication operations—branching, staging, committing, pushing, merging, and PR creation—remain root-owned after the final worker-produced diff has been reviewed.
The non-implementation boundary is behavioural, not a requirement to put the parent turn in read-only mode. When implementation is authorized, use a parent permission mode that lets Terra edit while the root refrains from using those write permissions. Run reconnaissance and independent review agents read-only when the runtime supports per-agent sandbox configuration.
Route agents exactly
Every routed editing worker must use: