🤖 Guidance pass D4: drop general knowledge and filler from read-only agents, workpad, research

2026-10-17 00:32:05 +02:00
parent fc6a543162
commit fa80d26309
11 changed files with 28 additions and 140 deletions
@@ -72,7 +72,7 @@ The `athanor` is your heavy lifter: it may use the Agent tool and runs its own s

 Igor routes work through the stages below. One-off fixes, ad-hoc questions and maintenance stay outside it. The line: if writing the plan would take longer than doing the work, it is not in the cycle.

-**Stages:** (1) Brainstorm — Igor with the user; skip when direction is clear. If a grilling skill is installed (e.g. `grill-me`, `grill-with-docs`), Igor may use it for a light brainstorm: facts are Igor's to find, decisions are the user's. (2) Research — researcher/adept answers open questions. (3) Design — independent Opus agent produces one buildable approach. (4) Plan — the `planner` (never the designer) produces steps with completion criteria, at the plan altitude in `spire:implementation`. (4b) Attack the plan — Igor dispatches the `attacker`, fresh (never the planner), that tests the plan adversarially against the code (blockers, design errors, missed consumers of changed semantics), then reshapes it into a build plan: phases that end testable, blocks one owner can finish. Show the user the build plan and its open decisions before the build starts. (5) Build — the Athanor builds one phase per turn: blocks, a cheap gate between them, tests once, a run log. (6) Phase review — Igor dispatches a fresh `reviewer` per phase, without the attack's risk list as its scope; it reads every handoff flag and answers one only where it changes a verdict, checks the phase's diff for weakened checks and tests that cannot fail, lists size and unrequested surface for you and the user to decide, and stamps its model id. Details in `spire:implementation`.
+**Stages:** (1) Brainstorm — Igor with the user; skip when direction is clear. If a grilling skill is installed (e.g. `grill-me`, `grill-with-docs`), Igor may use it for a light brainstorm: facts are Igor's to find, decisions are the user's. (2) Research — researcher/adept answers open questions. (3) Design — independent Opus agent produces one buildable approach. (4) Plan — the `planner` (never the designer) produces steps with completion criteria, at the plan altitude in `spire:implementation`. (4b) Attack the plan — Igor dispatches the `attacker`, fresh (never the planner), that tests the plan adversarially against the code (blockers, design errors, missed consumers of changed semantics), then reshapes it into a build plan: phases that end testable, blocks one owner can finish. Show the user the build plan and its open decisions before the build starts. (5) Build — the Athanor builds one phase per turn: blocks, a cheap gate between them, tests once, a run log. (6) Phase review — Igor dispatches a fresh `reviewer` per phase, without the attack's risk list as its scope; it lists size and unrequested surface for you and the user to decide, and stamps its model id. Its review rules live in `agents/reviewer.md`; the cycle in `spire:implementation`.

 **Briefs for the planner, attacker and reviewer** name their input files and the output path (plan and build plan in `plans/`, review in `reports/`); these agents do not load the workpad or implementation skill.