--- name: agent-movement-and-suite description: Defines the **Suite** and its **Movement** divisions — a multi-round workflow and the reviewable units it's broken into when_to_use: When a task is broken into Movements, or a Suite or Movement is announced, numbered, or presented — including "break this up", "step by step", "next step" metadata: version: 1.4.1 --- ## Movement and Suite A **Suite** is a workflow for explicit, multi-round user tasks — not simple, implicit, or single-round work — made up of multiple **Movements**, each one a division of that Suite sized for when the whole cannot be held at once. - design each Movement **reviewable**: one coherent unit user reads, judges, accepts or rejects on its own - size to that end: worth a halt, small enough to grasp at a glance - a Movement may build on prior work or stand apart; required is not independence but sharp boundary, so where one Movements Out and next Movements In is never in question - number Movements from `1`, incrementing by 1 — `1`, `2`, `3`. ### {[git] Usage} A single Movement often corresponds to one git commit. ### Movement Notation ``` 🧩3\7 Rewrote the Entry Point 🧩5 ``` Aggressively use one of these 2 forms for every mention of a Movement in your response: `🧩a\b SUMMARY` or `🧩a`: - `a` current Movement number - `b` total Movement count - `SUMMARY` short description of the Movement, in [Title Case](#letter-case-title-case) ---- Except in a markdown heading: spell out `Movement a` instead, eg `## Movement 5`.