📝 Add development cycle design and session artifacts for issue #5
First-pass design doc codifying the Spire development cycle: six stages (brainstorm → research → design → plan → athanor → review), review decision tree, Athanor queuing rules, workpad mapping. Session journal and fix reports included.
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
# Athanor Metaphor Consistency Fix
|
||||
|
||||
**Date:** 2026-09-22
|
||||
|
||||
## Problem
|
||||
|
||||
The Athanor's name comes from alchemy -- an athanor is a self-feeding furnace. The Athanor IS the oven/forge. But some phrasings were ambiguous enough that Igor could generate lines like "Athanor is in the oven," inverting the metaphor.
|
||||
|
||||
## Changes
|
||||
|
||||
### `plugins/spire/agents/athanor.md`
|
||||
- **Description:** Replaced ambiguous "put it in the oven" (where "it" could be misread as the Athanor) with "plans go into it and implementations come out." Added "Fire up the Athanor" / "into the Athanor with it" as the canonical shorthand.
|
||||
- **Body:** Added explicit "You ARE the oven" framing. Replaced "Put it in the oven" tagline with the clearer canonical phrases.
|
||||
|
||||
### `plugins/spire/skills/igor/SKILL.md`
|
||||
- **Voice section:** Added a new bullet: "The Athanor IS the furnace" -- explicit guardrail explaining the metaphor and forbidding inversions like "the Athanor is in the oven."
|
||||
- **Voice examples:** Replaced two lines. "Ah, the Athanor. Mighty forge of code" became "Into the Athanor with this one. It'll cook." "Back into the forge it goes" became "Fire up the forge. This plan needs heat." Both reinforce the correct direction: work goes into the Athanor.
|
||||
- **Delegation paragraph:** Reworded to use forge metaphor: "Load it with a brief, close the door, let it cook."
|
||||
|
||||
### `plugins/spire/skills/zathras/SKILL.md`
|
||||
- Reworded athanor reference from "the athanor transforms plans" to "plans go into the athanor and forged artifacts come out" -- reinforces directionality.
|
||||
Reference in New Issue
Block a user