Plan covers: stale tome.just path (quick fix), curator stub skill
(minimal first step), and journal graduation-candidate signal
(journal template + wrap-up update). Design questions deferred
for findings 4 and 6; actionable first steps defined for all three.
Fable-authored report comparing how each plugin handles project
adoption/init and cross-session knowledge accumulation. Surfaces
six gaps including missing spire:init, unshipped adept scaffolding,
and a stale tome.just path from the extraction commit.
When a ticket context is active (user named a ticket, ticket skill
opened one, or explicit request), task-scoped artifacts route into the
ticket folder while journals and goals stay in the main workpad.
Research and specs are a judgment call based on reusability.
Also: tighten resolution step 3 to distinguish project-level tickets
folder from per-ticket context, add ticket lifecycle to the "does not
cover" list, update steering section to include ticket routing.
Enable spire@reliquary, remove g4b_ai@reliquary and the dead
workpad@reliquary entry. Update root CLAUDE.md references to point
at Spire skills and agents instead of g4b_ai.
Voice section: Spire fixtures are real to Igor — one dry flourish per
named concept, then immediately proceed with the work. Theatrics face
the user only; briefs and journals stay plain.
Rules: a declined follow-up ("no") is a lull, not a stop — use it to
save the journal and close the beat with one line.
Igor's references/project.md ships read-only in the plugin cache with no
mechanism for per-project override. Projects can't fill in the template,
so Igor rediscovers basics each session. This goal captures the fix:
project-local resolution, an init skill, and /assistant alias docs.
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)
Plugin name: Spire. Orchestrator renamed from Forge to Athanor
("put it in the oven"). Trope reframed from mage tower to
alchemist's tower to bridge lab-fiction and arcane registers.
Design spec for the g4b_ai replacement plugin — component inventory,
deployment model, architecture, and existence map. Fable naming review
evaluates candidates and recommends "Keep" as the plugin name.
Add plugin skeleton with versioned skill directories, TODO SKILL.md
scaffolds with goals for skill-creator, and copy over bevy-skill-research
reports from spacecraft into docs/workpad/research/.
Three tool-restricted agents (scout/search/researcher) that cannot
spawn sub-agents, plus a research skill that prevents recursive
agent chains and caps web fetching.
Extract inline SVG rules to references/inline-svg.md for progressive
disclosure. Add references/layout-legibility.md with 7 rules for
readable SVG output (text sizing, contrast, margins, chart patterns,
palettes) based on concrete failure modes from issue #4.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Ports dirigent's gitea scripts into a self-contained reliquary plugin.
Scripts run via uv with PEP 723 inline deps — no project venv needed.
Gitea connection inferred from `git remote get-url origin` with env-var
overrides; only GITEA_TOKEN is mandatory. Workpad path and tickets
directory are parameterized so the plugin works in any project. Label
set externalized to labels.default.json with project-level override via
.gitea-labels.json.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Folds in decisions made during the design review: flat sibling imports
+ PEP 723, CWD-based paths, git-remote inference with env overrides,
workpad/tickets parameterization, project label overrides.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Probe now emits KEY=VALUE so the agent reads facts instead of inferring
from prose. Stdlib-only (no tomllib) so it runs on whatever Python the
launcher reaches. Adds sh/ps1 launcher pair, SCRIPTS_UV/SCRIPTS_DIR/
SCRIPTS_STORE env-var contract, tainted-venv + recipe + default-package
detection, and broader mode classification (incl. agent-tool-only).
SKILL.md trimmed and gated by pyproject.toml glob.
Introduce two new plugins: dioxus and project-uv with metadata
READMEs and SKILL documentation and example skill files
Update marketplace.json to advertise both plugins
Add exploratory and design docs for porting dirigent skills to
reliquary, including:
- Explore port options for the gitea skill (in-plugin vs vendored)
- Document activation mechanics across Claude Code and cross-tools
- Include an orchestration comparison between dirigent and reliquary
approaches
- Add research on glob negation and flag-file activation patterns
- Create uv-detection goals and skill-engines cross-tool reports
- Provide a research plan for future porting work and risk notes
The single ai-skills plugin becomes plugins/g4b_ai/ inside a
reliquary-named Claude marketplace. Root README/CLAUDE.md now
describe the marketplace; the plugin's own docs move alongside it.
This makes room for additional themed plugins and non-Claude
formats in parallel.
Move skills/ to repo root and add .claude-plugin/{plugin,marketplace}.json
so the skills can be installed in other projects via a local marketplace.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>