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

🤖 Fix agent write capabilities, Athanor metaphor, and delegation guidance

Browse Source 
Addresses Gitea issue #5 (Agent Rails): Explore/Plan agent types are
read-only but were recommended for tasks that need to write artifacts.
Replaced with write-capability guard in model-tiers.md, steered delegation
to scout/search/researcher. Tightened Athanor metaphor across all skills
— it IS the oven, plans go into it. Fixed assistant skill to route to Igor.
This commit is contained in:
g4borg
2026-09-22 13:48:33 +02:00
parent dcb765a760
commit bfa13312f0
6 changed files with 54 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/spire/skills/igor/references/model-tiers.md
+17 -9
View File
@@ -2,14 +2,16 @@
Prefer a project-pinned agent from `.claude/agents/` when one matches the task; the tiers below are the fallback and the rationale.
| Task type | Tier | Rationale |
|-----------|------|-----------|
| Domain knowledge, repeated consultation | `adept` agent (Opus, long-lived) | Accumulated priors, informed search, journal continuity; domain-scoped |
| Deep research, bug investigation | Opus-tier research agent | Depth, reasoning; writes reports, never modifies code |
| Planned implementation | implementer agent | Executes plans, verifies with the project's check/test commands |
| Multi-part jobs needing their own subagent fan-out | `athanor` (Opus-tier, may use Agent/Task tool) | Decomposes a brief and runs its own subagents |
| Complex summaries, git fixes, small code changes | Sonnet subagent | Capability/speed balance |
| Test runs, compiles, commits, linear-data summaries | Haiku subagent | Fast, cheap, mechanical |
| Task type | Tier | `subagent_type` | Rationale |
|-----------|------|-----------------|-----------|
| Domain knowledge, repeated consultation | `adept` agent (Opus, long-lived) | `"adept"` | Accumulated priors, informed search, journal continuity; domain-scoped |
| Deep research, bug investigation | Opus-tier research agent | `"researcher"` | Depth, reasoning; writes reports, never modifies code |
| Quick fact extraction, version/config lookup | Haiku lookup | `"scout"` | Fast, cheap, read-only; at most 2 web pages |
| Code/file lookups, symbol tracing | Sonnet search | `"search"` | Read-only; targeted "where is X" lookups |
| Planned implementation | implementer agent | project-pinned or omit (defaults to general-purpose) | Executes plans, verifies with the project's check/test commands |
| Multi-part jobs needing their own subagent fan-out | `athanor` (Opus-tier, may use Agent/Task tool) | `"athanor"` | Decomposes a brief and runs its own subagents |
| Complex summaries, git fixes, small code changes | Sonnet subagent | omit (defaults to general-purpose) | Capability/speed balance; needs write access |
| Test runs, compiles, commits, linear-data summaries | Haiku subagent | omit (defaults to general-purpose) | Fast, cheap, mechanical; needs Bash and possibly write access |
Rules of thumb:
@@ -17,9 +19,15 @@ Rules of thumb:
- A job with 3+ independent subtasks, or research + implementation combined, goes to `athanor` as a single brief (scope, output paths, completion criteria).
- When unsure between tiers, prefer the cheaper tier and escalate on failure.
Write-capability guard:
- **`Explore` and `Plan` are READ-ONLY.** They cannot use Edit, Write, or NotebookEdit. Never dispatch them for tasks that must produce a file artifact (report, design, plan, research note). Use them only for pure lookups (`Explore`) or pure planning conversations (`Plan`) where the answer comes back in the agent's reply text, not as a written file.
- **Prefer Spire's pinned read-only agents over `Explore`.** `scout` (Haiku), `search` (Sonnet), and `researcher` (Opus, can write) are purpose-built and tool-restricted. Use `scout` or `search` for lookups instead of `Explore`.
- **For tasks that produce file output, use write-capable agent types.** Omit `subagent_type` (defaults to general-purpose) or use a project-pinned agent that has Edit/Write (`researcher`, `adept`, `athanor`). The `researcher` agent is the correct choice for research that must produce a written report.
Sub-delegation guard:
- **Sub-delegation guard.** Agent types without the Agent tool cannot spawn children: `Explore` (read-only search) and `Plan` (design) are safe leaves. `general-purpose` and research/implementer agents may have the Agent tool and *can* sub-delegate — give them explicit "do not delegate" instructions, or route fan-out work to `athanor` on purpose. Only ever expect a second, differently-`task-id`'d notification when you dispatched something that was allowed to fan out.
- **Sub-delegation guard.** Agent types without the Agent tool cannot spawn children: `scout`, `search`, `Explore`, and `Plan` are safe leaves. `general-purpose` and `researcher`/implementer agents may have the Agent tool and *can* sub-delegate — give them explicit "do not delegate" instructions, or route fan-out work to `athanor` on purpose. Only ever expect a second, differently-`task-id`'d notification when you dispatched something that was allowed to fan out.
Model selection rules: