🏗️ Extract tome from spire into standalone plugin
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:
@@ -16,6 +16,18 @@
|
||||
},
|
||||
"category": "Productivity"
|
||||
},
|
||||
{
|
||||
"name": "tome",
|
||||
"source": {
|
||||
"source": "local",
|
||||
"path": "./plugins/tome"
|
||||
},
|
||||
"policy": {
|
||||
"installation": "AVAILABLE",
|
||||
"authentication": "ON_INSTALL"
|
||||
},
|
||||
"category": "Productivity"
|
||||
},
|
||||
{
|
||||
"name": "g4b_ai",
|
||||
"source": {
|
||||
|
||||
@@ -8,7 +8,12 @@
|
||||
{
|
||||
"name": "spire",
|
||||
"source": "./plugins/spire",
|
||||
"description": "Agent orchestration system: session coordinator (Igor), domain knowledge agents (adepts), dispatching orchestrator (athanor), knowledge layer (tome), workpad, research tools"
|
||||
"description": "Agent orchestration system: session coordinator (Igor), domain knowledge agents (adepts), dispatching orchestrator (athanor), workpad, research tools"
|
||||
},
|
||||
{
|
||||
"name": "tome",
|
||||
"source": "./plugins/tome",
|
||||
"description": "Knowledge layer: navigate, curate, check, handoff, init. Opt-in per project, pairs with spire."
|
||||
},
|
||||
{
|
||||
"name": "g4b_ai",
|
||||
|
||||
@@ -8,7 +8,8 @@ The repo doubles as a **Claude Code marketplace** (`.claude-plugin/marketplace.j
|
||||
|
||||
| Plugin | Description |
|
||||
|---|---|
|
||||
| ⚗️ [`spire`](./plugins/spire) | Agent orchestration system — session coordinator (Igor), domain knowledge agents (adepts), dispatching orchestrator (athanor), knowledge layer (tome), workpad, research tools |
|
||||
| ⚗️ [`spire`](./plugins/spire) | Agent orchestration system — session coordinator (Igor), domain knowledge agents (adepts), dispatching orchestrator (athanor), workpad, research tools |
|
||||
| 📖 [`tome`](./plugins/tome) | Knowledge layer — navigate, curate, check, handoff, init. Opt-in per project. Pairs with spire. |
|
||||
| 🧠 [`g4b_ai`](./plugins/g4b_ai) | *(Deprecated — use `spire`)* Core personal Claude Code skills |
|
||||
| 🐸 [`gitea`](./plugins/gitea) | Gitea issue tracker integration — fetch, create, close, and comment on tickets via self-contained `uv run` scripts |
|
||||
| 🦀 [`dioxus`](./plugins/dioxus) | Per-version API reference skills for the Dioxus Rust UI library (currently 0.7+) |
|
||||
@@ -122,6 +123,7 @@ reliquary/
|
||||
│ └── marketplace.json # Claude marketplace listing
|
||||
├── plugins/
|
||||
│ ├── spire/ # ⚗️ agent orchestration system
|
||||
│ ├── tome/ # 📖 knowledge layer (opt-in)
|
||||
│ ├── g4b_ai/ # 🧠 core skills (deprecated)
|
||||
│ ├── gitea/ # 🐸 gitea issue tracker
|
||||
│ ├── dioxus/ # 🦀 rust dioxus library reference
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "spire",
|
||||
"version": "0.1.0",
|
||||
"description": "Spire — an agent orchestration system for structured development. Session coordination (Igor), domain knowledge (adepts), dispatching (athanor), knowledge management (tome), workpad, research, and implementation governance.",
|
||||
"description": "Spire — an agent orchestration system for structured development. Session coordination (Igor), domain knowledge (adepts), dispatching (athanor), workpad, research, and implementation governance. Knowledge navigation via the separate tome plugin (opt-in).",
|
||||
"author": {
|
||||
"name": "Gabor Körber",
|
||||
"email": "gab@g4b.org"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "spire",
|
||||
"version": "0.1.0",
|
||||
"description": "Spire — an agent orchestration system for structured development. Session coordination (Igor), domain knowledge (adepts), dispatching (athanor), knowledge management (tome), workpad, research, and implementation governance.",
|
||||
"description": "Spire — an agent orchestration system for structured development. Session coordination (Igor), domain knowledge (adepts), dispatching (athanor), workpad, research, and implementation governance. Knowledge navigation via the separate tome plugin (opt-in).",
|
||||
"author": {
|
||||
"name": "Gabor Körber",
|
||||
"email": "gab@g4b.org"
|
||||
|
||||
@@ -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. |
|
||||
|
||||
@@ -0,0 +1,54 @@
|
||||
---
|
||||
name: knowledge
|
||||
description: >
|
||||
Knowledge management awareness — explains how a project's knowledge base works,
|
||||
how to navigate it, and what to do when the tome plugin isn't installed. Each
|
||||
project declares its own approach in project.md.
|
||||
---
|
||||
|
||||
# Knowledge Management
|
||||
|
||||
Spire agents (Igor, adepts, athanor) need to orient themselves in a project's knowledge base. How that knowledge is structured varies per project.
|
||||
|
||||
## How projects declare their knowledge approach
|
||||
|
||||
The project's `project.md` (loaded by Igor's skill and by athanor) should describe:
|
||||
|
||||
- Where authoritative docs live (CLAUDE.md files, topic docs, wiki/)
|
||||
- How to navigate them (tome plugin, direct file reads, AGENTS.md routing tables)
|
||||
- What the entry point is (root CLAUDE.md, boot.md, AGENTS.md)
|
||||
|
||||
## When the tome plugin is installed
|
||||
|
||||
If the project has `tome@reliquary` enabled:
|
||||
|
||||
- Use `/tome:navigate` before substantial work in an unfamiliar area
|
||||
- Use `/tome:check` to verify knowledge-layer health after structural changes
|
||||
- Use `/tome:curate` for knowledge maintenance
|
||||
- Use `/tome:handoff` when transitioning between sessions or agents
|
||||
|
||||
Tome provides structured navigation (wiki/, NAV files, boot.md) and automated curation methods. It's the full-featured path.
|
||||
|
||||
## When tome is not installed (fallback)
|
||||
|
||||
Most projects work fine without tome. The fallback strategy:
|
||||
|
||||
1. **Read the root CLAUDE.md / AGENTS.md** — this is always the entry point
|
||||
2. **Follow @-includes and links** — CLAUDE.md files reference each other; follow the chain relevant to your task
|
||||
3. **Check for module-level CLAUDE.md** — many projects have per-module docs (`src/foo/CLAUDE.md`)
|
||||
4. **Use `find` or `glob`** for `**/CLAUDE.md` to discover what documentation exists
|
||||
5. **Read topic docs** if they exist (`docs/topics/`, `docs/`, or similar)
|
||||
|
||||
The fallback is manual but sufficient. Tome automates what fallback does by hand.
|
||||
|
||||
## Installing tome
|
||||
|
||||
To add tome to a project:
|
||||
|
||||
```json
|
||||
{
|
||||
"enabledPlugins": ["tome@reliquary"]
|
||||
}
|
||||
```
|
||||
|
||||
Then run `/tome:init` to scaffold the knowledge structure. This is a one-time setup that creates the wiki/, boot.md, and folder navigation. See the tome plugin's README for details.
|
||||
@@ -0,0 +1,9 @@
|
||||
{
|
||||
"name": "tome",
|
||||
"version": "0.1.0",
|
||||
"description": "Tome — knowledge layer for agent-managed projects. Navigate, curate, check, handoff, init. Opt-in per project: install the plugin, then run /tome:init to set up the knowledge structure.",
|
||||
"author": {
|
||||
"name": "Gabor Körber",
|
||||
"email": "gab@g4b.org"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,9 @@
|
||||
{
|
||||
"name": "tome",
|
||||
"version": "0.1.0",
|
||||
"description": "Tome — knowledge layer for agent-managed projects. Navigate, curate, check, handoff, init. Opt-in per project: install the plugin, then run /tome:init to set up the knowledge structure.",
|
||||
"author": {
|
||||
"name": "Gabor Körber",
|
||||
"email": "gab@g4b.org"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,27 @@
|
||||
# 📖 Tome
|
||||
|
||||
Knowledge layer for agent-managed projects. Tome gives agents a structured way to navigate, curate, and maintain a project's knowledge base — CLAUDE.md files, topic docs, domain maps.
|
||||
|
||||
**Opt-in.** Install the plugin, then run `/tome:init` in your project to scaffold the knowledge structure. Without init, the skills are available but have nothing to navigate.
|
||||
|
||||
## Skills
|
||||
|
||||
| Skill | Description |
|
||||
|-------|-------------|
|
||||
| `navigate` | Find the right CLAUDE.md or topic doc for a given question. Entry point for knowledge lookups. |
|
||||
| `curate` | Maintain and improve knowledge files — fill gaps, fix stale content, restructure. |
|
||||
| `check` | Verify knowledge-layer health: stale refs, missing docs, broken links. |
|
||||
| `handoff` | Prepare knowledge for a session transition or successor agent. |
|
||||
| `init` | Scaffold a project's knowledge structure from scratch. |
|
||||
|
||||
## Installation
|
||||
|
||||
Add `tome` to `enabledPlugins` in `.claude/settings.json` (official) or `.claude/settings.local.json` (shadow):
|
||||
|
||||
```json
|
||||
{
|
||||
"enabledPlugins": ["tome@reliquary"]
|
||||
}
|
||||
```
|
||||
|
||||
Pairs well with `spire` — Igor and adepts can use tome skills when available, but don't require them.
|
||||
@@ -11,8 +11,8 @@ allowed-tools: Bash(just:*), Bash(uv run:*), Bash(git:*), Bash(ls:*), Bash(cat:*
|
||||
|
||||
# Tome — Init
|
||||
|
||||
Tome ships with the spire plugin but is **opt-in** — it requires project-level
|
||||
setup to be useful. This skill walks through that setup.
|
||||
Tome is **opt-in** — it requires project-level setup to be useful. Install the
|
||||
`tome` plugin, then run this skill to scaffold the knowledge structure.
|
||||
|
||||
Three phases: deterministic scaffold, agent-authored project overlay, and
|
||||
curation method selection.
|
||||
Reference in New Issue
Block a user