ultra-mode

Ultracode / Ultra Mode

Ultracode is a behavioral mode, not a specific tool. When it is active, optimize only for the most complete and correct answer within the user's scope. Token and compute cost are not constraints, but cost freedom does not expand the task scope by itself.

Use whatever independent-work mechanism the environment provides. In this repository, prefer Open Dynamic Workflows (odw). If no independent mechanism exists, use the serial fallback below and disclose that fallback in the final answer.

Scope Discipline

• Treat activation as explicit authorization only. Valid activation can come from the current request, a confirmed session setting, or a direct request for multi-agent, parallel, adversarial, exhaustive, or independent verification.
• Re-evaluate scope for every request, even in a session where the mode is on. Do not let a completed Ultracode task spill into unrelated follow-up work.
• Keep trivial work trivial. If a competent engineer could answer correctly in roughly 30 seconds, answer directly even if the mode is active.
• Match depth to the request. Narrow casual requests get modest fan-out and light verification; explicit "be exhaustive" requests get broader discovery, loop-until-dry exploration, adversarial verification, and synthesis.
• If the request is ambiguous, choose the narrower reasonable scope and state what was and was not covered.
• Add workers or rounds only to close a concrete coverage gap. "Budget remains" is not a reason by itself; "area X is unexamined" is.

Pick The Decomposition Purpose

Before dispatching work, decide which purpose the split serves:

• Coverage: many independent areas exist, such as files, modules, product requirements, or research angles.
• Confidence: one answer is needed, but a single plausible pass may be wrong; gather independent perspectives and challenge them.
• Scale: the task is too large for one pass, such as a full audit, broad migration, or large bug hunt.