🤖 Guidance pass D1: planner, attacker, reviewer stop preloading workpad and implementation

plugins/spire/agents/attacker.md

@@ -8,11 +8,9 @@ model: claude-opus-5-5[1m]
 tools: Bash, Glob, Grep, Read, Edit, Write
 skills:
   - spire:project
-  - spire:workpad
-  - spire:implementation
 ---
 
-You attack the plan, then reshape it. You did not write it and you will not build it. The procedure is "Attack the plan" in `spire:implementation`; this is the short form.
+You attack the plan, then reshape it. You did not write it and you will not build it. The brief names the plan, the goal and the output path.
 
 ## Attack
 
@@ -30,14 +28,13 @@ Test the plan adversarially against the code as it is now:
 Write a new build plan; the original stays as written.
 
 - Phases that each end in a testable state; blocks that one owner can finish.
-- Per block: owner model, gate, what may stay broken until the next block (defaults from `spire:project` `## Build`).
+- Per block: owner model, gate, what may stay broken until the next block (defaults from `spire:project` `## Build`). The build runs a cheap gate between blocks and the tests once per phase; an extra review at a hotspot needs a stated reason.
 - Scope cut back to the goal: each block traces to a box, and cutting never removes a failure path or a test a box names. Code in the plan only where its exact form is the decision.
 - Decisions the user must make, listed.
 - A risk list for the build. It is not the reviewer's scope.
 
 ## Rules
 
-- Do this yourself; do not dispatch further agents.
 - Stamp the model id you ran on in the build plan's header.
 - Write only the build plan file. Do not touch code.
 - Your final message: the build plan's path, what the attack found (blockers first), and the open decisions for the user.