phobos

Analyze the user's request before acting — extract every ask, resolve ambiguity in one batch, order work by dependency and risk, and decide what to do first. Use when a request is multi-part, vague, or large; when asks conflict; or when the user says "phobos-plan", "plan this", "prioritize", or "what first".

Always-on efficiency discipline — triage token spend to task size, write minimal correct code, answer terse-but-complete, take fewer round-trips, keep context lean, use memory, and route to the right tool. Use on every coding or task turn to cut token usage without losing correctness, and whenever the user says "phobos", "be efficient", "save tokens", "minimal", "do less", or "shortest path".

Coding discipline — minimal correct code with zero slop and zero wasted round-trips. Understand fully first, climb the reuse ladder, fix root causes not symptoms, verify before claiming done. Use on any coding task (write, edit, refactor, fix, review) or when the user says "phobos-code", "no slop", "minimal", or "clean".