ワンクリックで
ctx-journal-enrich
Enrich journal entry with metadata. Use when journal entries lack frontmatter, tags, or summary for future reference.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Enrich journal entry with metadata. Use when journal entries lack frontmatter, tags, or summary for future reference.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
EXPERIMENTAL (discardable). Hand a loose intent spec (.context/specs/intent-<slug>.md) off to spec-kit's /speckit-specify with a prose synopsis. Optional and graceful — warns and continues if spec-kit is not installed; the intent spec stands either way. Third step of the experimental chain.
EXPERIMENTAL (discardable). Stress-test a plan through adversarial interview, then write a debated brief to .context/briefs/<TS>-<slug>.md. First step of the experimental spec-kit delegation chain: /ctx-experimental-plan → /ctx-experimental-spec → /ctx-experimental-handoff.
EXPERIMENTAL (discardable). Turn a debated brief into a LOOSE intent spec at .context/specs/intent-<slug>.md — deliberately not pre-shaped into spec-kit's template. Second step of the experimental chain: /ctx-experimental-plan → /ctx-experimental-spec → /ctx-experimental-handoff.
Run a disciplined "dream" triage pass over the gitignored ideas/ folder — classify each idea against the codebase and specs, and emit gated, provenance-bearing disposition proposals into the dreams/ notebook for human review. NEVER writes canonical memory and NEVER acts on a proposal. Use when invoked headlessly by the scheduler (cron `claude -p`) or when the user says "run the dream" / "dream over my ideas". The human reviews via /ctx-serendipity.
The human review "garden walk" over ctx-dream proposals. Reads pending proposals from the dreams/ notebook and walks the human through accept / reject / amend / skip, one at a time, substance-forward. Mechanical dispositions apply instantly; generative ones (merge, promote) are done here by reading the full source. Use when the user says "serendipity round", "review my dreams", "walk the garden", or "what did the dream find?". The dream proposes; serendipity disposes.
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.
| name | ctx-journal-enrich |
| description | Enrich journal entry with metadata. Use when journal entries lack frontmatter, tags, or summary for future reference. |
Enrich a session journal entry with structured metadata.
.state.json has a
locked date OR the frontmatter contains locked: true. Locked
files must not be modified: skip them silently. Check via:
ctx system mark-journal --check <filename> locked
or look for locked: true in the YAML frontmatter.ctx system mark-journal --check <filename> enriched or read
.state.json in the journal directory; confirm before overwritingThe user specifies a journal entry by partial match:
twinkly-stirring-kettle (slug)twinkly (partial slug)2026-01-24 (date)76fe2ab9 (short ID)Find matching files in the journal directory:
ls "$(ctx system bootstrap -q)/journal/"*.md | grep -i "<pattern>"
If multiple matches, show them and ask which one.
If no argument given, show recent unenriched entries by reading
.state.json in the journal directory and listing entries without
an enriched date:
# List unenriched entries using state file
CTX_PATH=$(ctx system bootstrap -q)
for f in "$CTX_PATH/journal/"*.md; do
name=$(basename "$f")
ctx system mark-journal --check "$name" enriched || echo "$f"
done | head -10
/ctx-journal-enrich twinkly-stirring-kettle
/ctx-journal-enrich twinkly
/ctx-journal-enrich 2026-01-24
/ctx-journal-enrich 76fe2ab9
Read the journal entry and extract:
---
title: "Session title"
date: 2026-01-27
model: claude-opus-4-6 # auto-populated at import
tokens_in: 234000 # auto-populated at import
tokens_out: 89000 # auto-populated at import
type: feature
outcome: completed
topics:
- authentication
- caching
technologies:
- go
- postgresql
libraries:
- cobra
- fatih/color
key_files:
- internal/auth/token.go
- internal/db/cache.go
---
Auto-populated fields (set during ctx journal import, do NOT overwrite):
date, time, project, session_id, model, tokens_in, tokens_out, branch
Type values:
| Type | When to use |
|---|---|
feature | Building new functionality |
bugfix | Fixing broken behavior |
refactor | Restructuring without behavior change |
exploration | Research, learning, experimentation |
debugging | Investigating issues |
documentation | Writing docs, comments, README |
Outcome values:
| Outcome | Meaning |
|---|---|
completed | Goal achieved |
partial | Some progress, work continues |
abandoned | Stopped pursuing this approach |
blocked | Waiting on external dependency |
If ## Summary says "[Add your summary...]", replace with 2-3 sentences
describing what was accomplished.
Scan the conversation and extract:
Decisions made: link to DECISIONS.md if persisted:
## Decisions
- Used Redis for caching ([D12](../DECISIONS.md#d12))
- Chose JWT over sessions (not yet persisted)
Learnings discovered: link to LEARNINGS.md if persisted:
## Learnings
- Token refresh requires cache invalidation ([L8](../LEARNINGS.md#l8))
- Go's defer runs LIFO (new insight)
Tasks completed/created:
## Tasks
- [x] Implement caching layer
- [ ] Add cache metrics (created this session)
ctx system mark-journal <filename> enriched
ctx journal site --build or make journal