ultracode-flowlisted

# UltraCode Flow ## Respect explicit Help precedence If the request explicitly invokes `$ultracode-help` or `ultracode-help`, do not reconstruct live state. Read `../ultracode-help/SKILL.md` and answer `flow` as a read-only Help topic. Show what is happening now in a form the user can understand in one pass and act on immediately. ## Stay read-only Do not write status files, edit configuration, run write-producing checks, regenerate adapters, or change the task merely to refresh the view. Read these resources completely: - `../ultracode/references/command-interface.md` - `../ultracode/references/control-and-status.md` Read `../ultracode/references/swarm-protocol.md` when delegated jobs, findings, or waves exist. Read `../ultracode/references/feature-verification.md` when a durable feature verification plan is active or in scope. ## Reconstruct current truth Use sources in this order: 1. current live task, plan, and collaboration state; 2. results and evidence already observed by the lead; 3. persisted `.ultracode/status.md`, when present; 4. repository history only when the user requests historical context. Classify freshness internally as `LIVE`, `STALE`, or `IDLE`, but present it in the user's language with a reason. For example, explain that data is not current because the last snapshot predates live work. Show the snapshot timestamp when relying on persisted state. Never treat a stale file as live truth. ## Keep tickets and agents distinct A ticket is a boun