mirror of
https://github.com/InsanusMokrassar/TelegramBotAPI.git
synced 2026-07-29 21:26:27 +00:00
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) <noreply@anthropic.com>
This commit is contained in:
@@ -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.)
|
||||
|
||||
Reference in New Issue
Block a user