Files
Paul Hernandez 5458c35b35 refactor(plugins): prefix Claude Code plugin skills with bm- (#878)
Signed-off-by: phernandez <paul@basicmachines.co>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-04 12:04:05 -05:00

1.7 KiB

title, type, entity, version, schema, settings
title type entity version schema settings
Decision schema Decision 1
decision rationale? alternative?(array) consequence?(array) context? affects?(array) supersedes?
string, the choice that was made string, why this choice over the alternatives string, options that were considered and not taken string, what this decision commits us to string, the situation that prompted the decision Entity, work or notes this decision bears on Entity, a prior decision this one replaces
validation frontmatter
warn
status?(enum, lifecycle of the decision) decided? project?
open
accepted
superseded
rejected
string, when the decision was made (ISO timestamp) string, the Basic Memory project this decision belongs to

Decision

A DecisionNote is a durable record of a real choice — one with alternatives and a rationale, not a passing preference. The Basic Memory plugin's output-style prompts Claude to capture these inline as decisions are made, and the future /basic-memory:bm-decide command captures them explicitly.

Decisions are found by structured recall: search_notes(metadata_filters={"type": "decision", "status": "open"}).

What makes a good DecisionNote

  • decision — state the choice plainly.
  • rationale + alternative — why this, and what was rejected. This is the part that saves a future session from relitigating the same ground.
  • consequence — what the choice commits the work to.
  • affects / supersedes — relations that wire the decision into the graph.

Frontmatter

type: decision plus status make decisions queryable. Capture decisions sparingly — one note per genuine decision, not per opinion. Validation is warn, never blocking.