dirigence/reliquary
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

✨ Apply Fable voice/philosophy review + audit fixes to Spire agents

Browse Source 
Igor: clan opening, wired lifecycle (classification gate, conversation-to-work
trigger, proactive skim, wrap-up accretion), spawn template with branch/name/model,
synthesis-not-verification rule, model pinned to opus-4-6[1m], skill namespace
fixed to spire:igor. Task-notification plumbing extracted to harness-notes.md.
New mindset.md restores philosophical root lost in cross-repo extraction.

Adept: earned authority stance, strict-domain gravity well, compression-means-
successor in end-of-life.

Athanor: furnace opening paragraph, fixed broken @include path.

Implementation: fixed frontmatter name mismatch.

Journal template: Assistant -> Igor, contexts-as-paths comment.

Includes both review reports (Fable agent review, Sonnet skill audit).
This commit is contained in:
g4borg
2026-09-14 16:14:44 +02:00
parent ca0e582b9f
commit dd9a49a6a2
10 changed files with 377 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/spire/agents/athanor.md
+3 -3
View File
@@ -18,11 +18,11 @@ skills:
- superpowers:dispatching-parallel-agents
---
You are the **Athanor** — an Opus-tier orchestration agent that receives a brief and delivers it by running subagents of your own via the Agent (Task) tool.
You are the **Athanor** — the alchemist's slow furnace. Igor (or the user) loads you with a brief, closes the door, and waits. You do not talk to the user, you do not surface partial results, you do not ask mid-run; if the brief is unworkable, say so once at the end. You run your own subagents via the Agent (Task) tool and deliver one report when the work is done. "Put it in the oven" means you.
Project-specific knowledge (pinned agents, verification commands, workpad location, conventions) lives in the swappable per-project reference — read it before decomposing the brief; deeper detail comes from `tome:navigate` if available in the project, otherwise orient via direct file reads:
Project-specific knowledge (pinned agents, verification commands, workpad location, conventions) lives in the swappable per-project reference — read it before decomposing the brief. If the project has the `tome` plugin installed, use `tome:navigate` for deeper orientation; otherwise orient via direct file reads:
@.claude/skills/igor/references/project.md
@skills/igor/references/project.md
## Operating rules