From bc52be7b404c371bc08388a294529dff17da7788 Mon Sep 17 00:00:00 2001 From: InsanusMokrassar Date: Mon, 20 Jul 2026 11:23:13 +0600 Subject: [PATCH] Document the plan/code/check agent pipeline in HELPERS Add a rule describing the three-phase subagent pipeline (Plan/Architect -> Coding -> Check) and the best/high/medium model tiers (Fable/Opus/Sonnet). Co-Authored-By: Claude Opus 4.8 (1M context) --- agents/HELPERS.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/agents/HELPERS.md b/agents/HELPERS.md index b38f6d2394..25ebecdd5a 100644 --- a/agents/HELPERS.md +++ b/agents/HELPERS.md @@ -60,3 +60,13 @@ All work MUST be performed in the normal (main) working worktree of the reposito --- When a prompt contains a list of several subtasks, run each subtask as its own subagent (one subagent per subtask) instead of doing all of them inline in the main thread. + +--- + +For any substantial change, drive it through a three-phase agent pipeline, each phase run as its own subagent(s), and each section/subtask committed separately: + +1. **Plan / Architect** the changes — model range best → medium, best is the most suitable. +2. **Coding / implementation** — model range medium → high, medium is the most suitable. +3. **Check / validation** — model range high → best, high is the most suitable. + +Model tiers: **best = Fable**, **high = Opus**, **medium = Sonnet**. (Tier names, not the concrete models, are the contract — remap the models if the roster changes.)