ワンクリックで
bm-decide
Capture a durable engineering decision in Basic Memory with rationale, alternatives, consequences, and affected work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Capture a durable engineering decision in Basic Memory with rationale, alternatives, consequences, and affected work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orient Claude from Basic Memory before substantial repo work by reading active tasks, open decisions, recent checkpoints, and repo conventions. Use when resuming old work or when the user asks where things stand.
Set up the Basic Memory plugin for this project — a short guided interview that configures the project mapping, seeds note schemas, learns or suggests placement conventions, and enables capture reflexes. Use when the user runs /basic-memory:bm-setup, says "set up basic memory", or asks to configure/bootstrap the plugin.
Show the Basic Memory plugin's current state for this project — active project, capture folders, output style, recent session checkpoints, and whether Basic Memory is reachable.
Save a deliberate Codex work checkpoint to Basic Memory with changed files, verification, decisions, blockers, and the next action.
Orient Codex from Basic Memory before substantial repo work by reading active tasks, decisions, recent Codex checkpoints, and repo conventions.
Set up Basic Memory for Codex at user or project level by mapping a Basic Memory project and seeding schemas.
| name | bm-decide |
| description | Capture a durable engineering decision in Basic Memory with rationale, alternatives, consequences, and affected work. |
Use this when the user makes or asks to record a durable choice. A decision is a choice with rationale and consequences, not a casual preference.
Resolve ~/.codex/basic-memory.json, then the nearest project
.codex/basic-memory.json; project keys override user keys:
primaryProject when setplacementConventions for the directory when they are specificdecisionsApply the bm-writing skill before drafting the note.
Clarify only if the choice itself is ambiguous. Do not ask for every field if the conversation already contains the rationale.
Write a type: decision note:
status: open unless the user says it is accepted, superseded, or rejecteddecided: <ISO timestamp when known>project: <primaryProject if known>Include:
Confirm with the permalink. If this supersedes an older decision, update the old
note or link it as supersedes.