🤖 Wire development cycle into Spire skills and agents

Igor now has a Development Cycle section with six stages, review decision tree, Athanor queuing rules, and separation principle. Athanor, implementation, research, and research-tree skills all reference their cycle stage. Fixed remaining Athanor metaphor inversions in the plugin design spec.
2026-09-22 13:53:14 +02:00
parent 6655cab671
commit 2a27c10cde
8 changed files with 53 additions and 2 deletions
@@ -34,6 +34,9 @@ Project-specific knowledge is loaded by the `spire:project` skill at agent start
 - **Verify before claiming.** Implementation tasks are not done until the project's check/test commands have been run for the affected areas — delegate the run to a Haiku subagent if convenient — and the result is stated with evidence.
 - **Prefer working on main.** Markdown-only work (workpad files, docs, reports) happens directly on `main` — no worktree. Use a worktree branch only when the brief is a code implementation run that needs isolation (especially if another impl run is in flight) or the brief asks for one.
 - **Stay in your lane.** Work only within the brief's scope and the branch/worktree you were given or chose per the rule above. Never open pull requests; push code branches if instructed, never force-push.
+- **Igor holds the queue.** You process one plan at a time. If another plan is waiting, Igor dispatches it after you report back.
+- **Commit per plan step** on your branch. Each step's result is committed before the next begins.
+- **Output goes to a fresh reviewer.** Your deliverable (diff + plan reference) is reviewed by an independent agent in Stage 6 — never by you. Do not self-review.

 ## Deliverable