| 1 | # Proposed AGENTS.md changes |
| 2 | |
| 3 | ## 1. Delete `## Orchestration` |
| 4 | |
| 5 | Nothing replaces it. The skill's description triggers on being asked to |
| 6 | orchestrate, maintain or run a project with sub-agents, on delegating several |
| 7 | tasks, and on resuming the role. The one rule every thread needs, "after |
| 8 | launching a sub-agent: nothing", already lives in Output Preferences. |
| 9 | |
| 10 | Where each old rule went: |
| 11 | |
| 12 | | Old rule | Skill | |
| 13 | | --- | --- | |
| 14 | | Main thread holds the plan, ownership and seam; sub-agents hold edits and deep planning | intro, §1, §3 | |
| 15 | | No acknowledgement or recap after launching; keep the parent run active | §10 | |
| 16 | | No final reply, even empty, while required work is pending | §10 | |
| 17 | | Review completed results, then report; surface questions with context | §1 (spot-check), §10 (questions) | |
| 18 | | The transcript records completed work; zero output when only queued work changed | §10 | |
| 19 | | Streamed tasks: none lost half-implemented; sub-agent questions surface with context | §1, §10 | |
| 20 | | Relay my words or another agent's over your own opinion | §10 | |
| 21 | | Full context and a concrete deliverable; independent agents in one message; self-review; spot-check the diff | §5, `references/brief.md`, §1 | |
| 22 | | Route by judgment: low / med / high | §4: model cards, account cards, and rules for adapting to quota | |
| 23 | | Floated ideas; a search agent only when the answer needs a lot of context | §1 | |
| 24 | | Run browser checks yourself | §1 | |
| 25 | | On request, split commits as work continues, crediting every model | §10; the trailer format stays in Jujutsu (`claude-opus-5.5`; the old example said `claude-opus-5`) | |
| 26 | |
| 27 | ## 2. Add compatibility to `## Code Quality` |
| 28 | |
| 29 | You called it "project specific or a global agent change if any". As a global |
| 30 | rule, after the shipped-contracts paragraph: |
| 31 | |
| 32 | ``` |
| 33 | Keep changes two-way compatible when you can: new code reads old data, and old |
| 34 | code reads new data. Propose a breaking or backwards-only change before making |
| 35 | it. |
| 36 | ``` |
| 37 | |
| 38 | The skill's §6 says the same for orchestrated work; with this line in |
| 39 | AGENTS.md, §6 can shrink to a pointer. |