| name | log |
| description | Record a manual entry in the active phase history file. Activates when the user invokes /log or asks momentum to run the log recipe. |
Record a manual entry in the active phase history file.
Steps
- Read
specs/status.md to identify the active phase
- Find the history file:
specs/phases/<active-phase>/history.md
- Determine entry type from the message:
- Decision about technology/architecture → [DECISION]
- Phase scope added/removed → [SCOPE_CHANGE]
- Bug/tech debt/enhancement found → [DISCOVERY]
- New planned feature → [FEATURE]
- Architecture pattern changed → [ARCH_CHANGE]
- Evaluator defined or changed → [EVALUATOR]
- Anything else → [NOTE]
- Extract or infer topics (2-5 keywords)
- Identify affects-phases (check
specs/phases/index.json)
- Identify affects-specs (check
specs/decisions/impact-map.json)
- Append the formatted entry to history.md (APPEND ONLY):
### [TYPE] YYYY-MM-DD — Short title (max 10 words)
Topics: topic-1, topic-2, topic-3
Affects-phases: phase-N-name (or "none")
Affects-specs: path/to/file.md#section (or "none")
Detail: One to three sentences describing what changed and why.
---
- If the entry introduces a topic not in
specs/decisions/impact-map.json, add it
- Confirm: "Logged [TYPE] entry to [phase] history."
