feature-codex-spectre-implementation

name	feature-codex-spectre-implementation
description	Use when modifying the Codex SPECTRE install flow, SessionStart continuity, project skill syncing, registry injection, or Codex-specific runtime files. TRIGGER when: codex, spectre, codex install, sessionstart, agents.override, registry, spectre-learn, spectre-recall, hooks.json, config.toml, doctor

Codex SPECTRE Implementation

Trigger: codex, spectre, codex install, sessionstart, agents.override, registry, spectre-learn, spectre-recall, hooks.json, config.toml, doctor Confidence: high Created: 2026-03-30 Updated: 2026-07-19 Version: 5

Current Design

Codex SPECTRE installs the workflow as Codex-native skills, subagent TOML configs, and generated SessionStart hooks. Project knowledge and session continuity are written into managed AGENTS.override.md blocks so hook output stays short.

Reusable project knowledge is both configured as normal skills and injected as a compact trigger registry:

• spectre-learn writes project skills under .agents/skills/{category}-{slug}/SKILL.md.
• The recall registry lives at .agents/skills/spectre-recall/references/registry.toon.
• spectre-recall is generated as an explicit search/load skill.
• Project installs sync .agents/skills/*/SKILL.md into Codex [[skills.config]].
• spectre-apply contains a {{REGISTRY}} placeholder that both the hook and src/lib/knowledge.js substitute before writing the managed knowledge block.
• bootstrap → handoff-resume → load-knowledge is the required SessionStart order.

Workflow task execution now uses a two-artifact contract: