Menu
Use before broad session renaming or semantic naming work to classify `.aoa` session archives by naming readiness, lower-layer blockers, and phase-discovery needs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a `.aoa` session-memory root must be created, installed, checked, repaired, or prepared for Codex hook-based session archiving.
Use when an indexed `.aoa` session needs provisional first-pass distillation into lessons, decisions, failures, and automation candidates without promoting them to reviewed truth.
Use when an agent needs evidence from prior `.aoa` sessions about how a skill, MCP, hook, tool, API, goal, eval, test, validator, script, decision, error, receipt, or other recurring operational entity was used, what happened nearby, and which raw or segment refs prove it.
Use in any Codex session when the user mentions `.aoa`, session memory, Codex transcripts, compaction, prior session rehydration, hook failures, or AoA session-memory validation.
Use when an agent needs to build or query the portable `.aoa` SQLite search index for archived Codex sessions, with evidence refs and freshness checks.
Use when the live Codex PreCompact and PostCompact hook path must be proven through `.aoa` using the Codex app-server compact probe.
| name | aoa-session-naming-readiness |
| description | Use before broad session renaming or semantic naming work to classify `.aoa` session archives by naming readiness, lower-layer blockers, and phase-discovery needs. |
| license | Apache-2.0 |
| metadata | {"aoa_scope":"session-memory","aoa_invocation_mode":"manual"} |
Use this before applying session names, semantic aliases, or physical relabels.
Naming is a pressure test of lower layers. Do not start by naming everything. Start by asking which sessions are ready, which need phase/topic discovery, and which must be repaired at raw/index level first.
SESSION_NAMES.md or sessions/INDEX.md feels too weak to navigate.name-session.Refresh the generated readiness maps:
python3 scripts/aoa_session_memory.py naming-readiness all \
--workspace-root <workspace-root> \
--aoa-root <aoa-root> \
--refresh-indexes \
--write-report
For a bounded window:
python3 scripts/aoa_session_memory.py naming-readiness all \
--workspace-root <workspace-root> \
--aoa-root <aoa-root> \
--since-days 21 \
--refresh-indexes \
--write-report
For one target:
python3 scripts/aoa_session_memory.py naming-readiness <session-label-or-id> \
--workspace-root <workspace-root> \
--aoa-root <aoa-root> \
--write-report
blocked: repair missing or unrecoverable raw/index state before naming.diagnostic_only: leave the raw-unavailable diagnostic visible unless a
transcript candidate appears.needs_reindex: refresh generated segments/indexes from preserved raw before
choosing a semantic name.needs_phase_discovery: inspect segments and create phase/topic candidates
before assigning a whole-session name.phase_discovery_ready: review the generated phase/topic candidate artifact
before applying a whole-session name.ready_for_semantic_name: apply a semantic session name with raw evidence
refs, not a blind folder rename.readable_label: keep the canonical label unless review finds a better
semantic name.low_signal: likely probe or tiny session; leave it unless it matters.named: verify or refine the existing semantic name.Do not use readiness as reviewed truth. It is a routing index for the next pass. Every applied semantic name still needs raw refs and bridge anchors.
For a session routed to phase_topic_discovery_before_session_name, generate
open candidates first:
python3 scripts/aoa_session_memory.py phase-discovery <session-label-or-id> \
--workspace-root <workspace-root> \
--aoa-root <aoa-root> \
--write \
--write-report
This writes naming/phase-discovery.json and .md inside the session. Treat
those files as review input, not applied names.