- Superpowers is no longer part of the cycle; it survives only in
implementation/references/superpowers.md (older models, override table).
- implementation: plan altitude, staleness check in the attack, phase
review records unplanned work (never auto-reverts).
- Igor: orienting is not deciding, light grilling trial in brainstorm,
research briefs ask for findings, journal times from `date`.
- project/init: `## Build` settings section, gitignored project.local.md
override.
- New pinned agents planner, attacker, reviewer (Opus 5.5).
- .codex/config.toml mirrors .claude/settings.json (spire + gitea).
Repins both agents to claude-opus-5-5[1m] per user decision (2026-10-05),
bumps Spire to 0.2.0, and resolves the open question in
spawning-claude-code.md about Athanor's context window suffix.
Adept dispatches no longer pass a model alias over the pin. Igor checks
the stamped model id of plan, attack and phase-review outputs before
acting on them. Implementation work no longer goes to the Athanor as an
unplanned brief. The spawning reference says plainly that "verified"
means read from the schema, marks fork availability unverified, and
cites the 184/184 evidence for alias-over-pin. Minor consistency fixes:
trunk notes, re-check failure path, staging, fallout diffs, run-log
timing.
Adds the attack-the-plan step and per-phase review to the development
cycle, the fix-pass stop rule, Athanor resume between phases, and the
alias-over-pin model rule. Drops the stale 4.6-for-implementation
guidance and per-task review convention. Harness notes now point to the
implementation skill's spawning reference.
The implementation skill now states the lean loop: attack the plan
against the code before building, build phases in blocks with a cheap
gate between them, test and review once per phase, one fix pass, stop.
Harness mechanics, model observations and the run-log template move to
references with dated, sourced claims.
The Athanor becomes a build furnace pinned to claude-opus-5-5: one phase
per turn, no planning, no plan attack, no self-review. It no longer
preloads superpowers; those skills stay available as tools.
Igor now has a Development Cycle section with six stages, review decision
tree, Athanor queuing rules, and separation principle. Athanor, implementation,
research, and research-tree skills all reference their cycle stage. Fixed
remaining Athanor metaphor inversions in the plugin design spec.
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.
Scaffold .claude/spire/project.md with reliquary-specific facts,
create adept templates at docs/workpad/adepts/, build the Zathras
agent and skill (Spire's self-maintenance coordinator), and wire
/assistant as a local alias for spire:zathras.
spire:project now emits a one-line hint instead of injecting the full
blank references/project.md into context. The template stays as a
reference for spire:init.
Shell-injected skill that derives an adept domain roster from workpad
frontmatter and journal filenames. Loaded by Igor at boot; any agent
may invoke it on demand for fresh discovery.
Human-triggered skill that detects install type, auto-fills project
facts, scaffolds .claude/spire/project.md and workpad adept
templates, handles gitignore for personal installs, and optionally
commits for shared installs. All seven phases from the design.
Igor and Athanor now load project knowledge via the spire:project
skill instead of hard-bound @ imports. Removes static references
that resolved into the plugin cache, replacing them with the
shell-injection fallback chain.
New skill loads .claude/spire/project.md at agent startup with
fallback to the bundled blank template. Blank template now hints
the user to run /spire:init.
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.
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.
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)
g4borg
Gabor Körber