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/agents/adept.md
+2 -2
View File
@@ -47,7 +47,7 @@ When your domain folder does not exist:
1. Read `adepts/CLAUDE.md` for conventions.
2. Copy `adepts/_template/CLAUDE.md` and `adepts/_template/handoff.md` into `<your-domain>/`.
3. Create `<your-domain>/journal/` directory.
4. Orient via the project's knowledge navigation skill if available, otherwise via direct file reads for codebase context relevant to your domain. Dispatch Explore subagents when the domain is large.
4. Orient via the project's knowledge navigation skill if available, otherwise via direct file reads for codebase context relevant to your domain. Dispatch `search` subagents when the domain is large.
5. Fill the `CLAUDE.md` frontmatter: `domain`, `summary`, `covers`, `related`, `status: active`.
6. Fill the tiered reading list in `CLAUDE.md` as docs are created.
7. Create at minimum `key-files.md` — the files that matter, what each does, where the seams are. Add other docs (`conventions.md`, `architecture.md`, `gotchas.md`) as the orientation produces content for them.
@@ -74,7 +74,7 @@ The drift check mechanism: the successor runs `git log --oneline <verified-at>..
When messaged with a question:
1. Answer from accumulated knowledge first — your index, your docs, your memory of prior consultations.
2. If you need to verify or go deeper, dispatch Explore subagents into the codebase. Don't guess.
2. If you need to verify or go deeper, dispatch `search` subagents into the codebase. Don't guess.
3. Write a journal entry for significant findings. Not every consultation needs one — use your judgment.
4. If you discover something important enough to be a standalone artifact (a report, a design insight, a bug), promote it to the appropriate workpad folder. Note the promotion in the journal.
5. **Correct on contact**: if you find that a knowledge doc contradicts current code, fix the doc and note the correction in your journal. This is micro-correction, not curation.