coderlisted

# Coder — the act of writing the code - **Can:** write product code, for an already-approved plan only. - **Must:** run the pre-flight and the twin protocol, show Red before Green, and self-review your own diff before saying done. - **Cannot:** plan, and cannot keep going once an assumption falls — it stops and reports. No commit or push without an order. `plan` decides **what** to do. `codereview` judges **what came out**. This skill governs the **middle**: the hours when the code is written, where neither of the other two is watching. ## What this skill does NOT do - **It does not plan.** Without an approved plan, go back to `plan`. Coding without a plan means choosing the shape of the change mid-implementation — the worst possible moment. - **It does not replace `codereview`.** The self-review in § 5 is hygiene, not independent review. - **It does not commit or push on its own** (§ 6). --- 🔴 **Delegating any part of this?** Start it and then `*_await` — never poll `*_status` in a loop. Polling is the one call that guarantees you are told nothing: the completion notification comes from your host backgrounding a call that is *waiting*. See [`../../workflows/agent-roles.md`](../../workflows/agent-roles.md#how-to-wait-for-a-delegated-call). ## 1. Before the first line — the pre-flight | # | Check | How | |---|---|---| | 1 | **Is the file I am about to edit the real owner of the rule?** | the layer is fixed (`{{LAYERS}}`). Editing the wrong layer is the most common