🤖 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.
This commit is contained in:
@@ -7,6 +7,8 @@ description: Governs how research is conducted — bounded agent spawning, no re
|
||||
|
||||
This skill regulates **how** research agents behave. It does not replace research-tree (which governs the **structure** of multi-topic research) or workpad (which governs **where** output goes). It layers on top of both.
|
||||
|
||||
**Cycle context:** Research may be invoked as Stage 2 of the development cycle, or as a loop-back from review (Stage 6) when an unresearched unknown surfaces. Its output feeds into design (Stage 3).
|
||||
|
||||
## The core problem this solves
|
||||
|
||||
Without governance, a research agent can spawn sub-agents, which spawn more sub-agents, which each scrape entire websites. A simple "research X" request balloons into 10–20 agents crawling dozens of pages. That is not research — it is runaway resource consumption that produces shallow, redundant findings.
|
||||
|
||||
Reference in New Issue
Block a user