メニュー
Save session findings, decisions, and discoveries back to Stele shared memory
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | checkpoint |
| description | Save session findings, decisions, and discoveries back to Stele shared memory |
| user-invocable | true |
Review the current conversation and persist important findings to Stele so other team members and future sessions benefit.
Look for the project's Stele scope in the current project's CLAUDE.md — find the "Stele Shared Memory Protocol" section and extract the scope from the **Scope:** line. If not found, ask the user.
Scan the current conversation for:
For each finding, determine the storage type and apply appropriate tags:
store_memory(
scope: "{scope}",
title: "{concise title}",
content: "{detailed description with context}",
memory_type: "{knowledge|decision|convention|troubleshooting|reference}",
tags: ["{appropriate tags}"]
)
Tagging convention:
| Tag | Meaning |
|---|---|
#active | Currently implemented and enforced rules |
#todo | Technical debt or pending migrations |
#contract | Inter-service API definitions and shared interfaces |
#breaking | Changes that require other agents/services to update |
#wisdom | Non-obvious technical discoveries and gotchas |
#conflict | Local rule that conflicts with a workspace-level rule |
Check the project entity in Stele for project-specific tags (seeded during /stele:bootstrap).
For new components or services discovered:
create_entities(
entities: [{name: "...", entity_type: "...", observations: ["..."]}],
scope: "{scope}"
)
For new observations about existing entities:
add_observations(
entity_name: "...",
scope: "{scope}",
observations: ["..."]
)
For discovered relationships:
create_relations(
relations: [{from: "...", to: "...", relation_type: "..."}],
scope: "{scope}"
)
Present a summary of what was saved:
Ask the user if anything was missed or if they want to add additional context to any item.
Clarify phase of the workflow chain. Uses Opus to analyze the user's request, resolve ambiguities, define scope, and produce a clear task brief before research begins.
Execute phase of the workflow chain. Uses Haiku (simple), Sonnet (standard), or Opus (complex) to implement code changes according to a plan. Use when the user has an approved plan ready to execute.
Flow workflow chain that runs clarify → [research] → plan → execute → validate end-to-end without stopping. Pauses only on genuine ambiguity or circuit-breaker conditions.
Plan phase of the workflow chain. Uses Opus to design an implementation strategy. Use when the user wants to create a detailed plan before executing changes.
Research phase of the workflow chain. Uses Haiku (simple) or Sonnet (standard) to research the codebase and gather context for a task. Use when the user wants to investigate code before planning.
Validate phase of the workflow chain. Uses Sonnet to review and validate implementation changes. Use when the user wants to validate that code changes are correct and complete.