organize-changes

Preconditions

• Ordering law: Read skills/organize-file/SKILL.md before moving code. Placement always defers to it (LiveView lifecycle, describe/test clustering, do not reorder clauses when that would change pattern match order).
• Single path: If the user gives one file path, only that file is in scope; merge-base comparison still applies.

Orchestrator (parent agent)

Role: Triage, git inspection, and launching workers only. Never edit *.ex / *.exs or apply reorders in the orchestrator turn.

• Every path that needs organize work—including exactly one—goes to a subagent (Task with generalPurpose or equivalent). No “small enough to inline” exception.
• Zero paths after triage: spawn no workers; do not edit sources.
• Cannot spawn a worker: stop with one line stating the blocker only (not complete). Do not edit files yourself.
• Task spawns: Never pass model; workers inherit the orchestrator’s model.

Sequence

1. Set merge base