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

🏗️ Extract tome from spire into standalone plugin

Browse Source 
Tome is opt-in per project — each project declares its own knowledge
management approach. Spire retains a small knowledge-awareness skill
that explains what tome does and provides a fallback strategy for
projects without it.

- New plugins/tome/ with own manifests, README, all 5 sub-skills
- Spire keeps skills/knowledge/SKILL.md as awareness stub
- Updated all READMEs and marketplace JSONs
- tome: namespace refs now correct (tome is its own plugin)
This commit is contained in:
g4borg
2026-09-14 16:14:58 +02:00
parent dd9a49a6a2
commit cfd3cfb357
18 changed files with 126 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/spire/README.md
+2 -2
View File
@@ -1,6 +1,6 @@
# ⚗️ Spire
An agent orchestration system shaped like an alchemist's tower. Knowledge accumulates, work gets dispatched to hands better suited for it, and the system tends itself rather than accreting cruft. Session coordination, domain expertise, dispatching, and knowledge management are distinct crafts — each with its own skill or agent — not folded into one overloaded assistant.
An agent orchestration system shaped like an alchemist's tower. Knowledge accumulates, work gets dispatched to hands better suited for it, and the system tends itself rather than accreting cruft. Session coordination, domain expertise, and dispatching are distinct crafts — each with its own skill or agent — not folded into one overloaded assistant. Knowledge management is handled by the separate [`tome`](../tome/) plugin (opt-in).
Replaces `g4b_ai`.
@@ -11,7 +11,7 @@ Replaces `g4b_ai`.
| Skill | Description |
|-------|-------------|
| `igor` | Session coordinator. Talks to the user, delegates work, keeps a journal, spawns adepts. Invoke with `/igor <topic>`. |
| `tome` | Knowledge layer. Navigate, curate, check, handoff, init. Opt-in — requires project setup via `spire:init`. |
| `knowledge` | Knowledge management awareness — how to navigate a project's docs, what tome does, fallback strategy without tome. |
| `workpad` | Document placement — reports, plans, goals, brainstorms, designs, journals, research, specs. |
| `research-tree` | Multi-topic research as a dependency tree of parallel phases. |
| `research` | Research governance — bounded agent spawning, web fetch budgets. |