Menu
Record a manual entry in the active phase history file. Activates when the user invokes /log or asks momentum to run the log recipe.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| 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.
specs/status.md to identify the active phasespecs/phases/<active-phase>/history.mdspecs/phases/index.json)specs/decisions/impact-map.json)### [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.
---
specs/decisions/impact-map.json, add itBegin a new implementation phase. Activates when the user invokes /start-phase or asks momentum to run the start-phase recipe.
Work with concurrent workstreams (Rule 15). Activates when the session involves multiple active branches, cross-lane coordination, or when starting work that should not live on the current branch.
Record a new backlog item (bug, feature, tech debt, or enhancement) when you discover work that needs tracking. Activates when the session identifies unplanned work that should be tracked in the backlog.
Check spec structure health of the momentum project. Activates when the user runs `/validate`, asks for a health check, or when spec changes need verification before phase completion.
>-
Drive a single repo through its phase as part of a swarm. Activates when spawned by the conductor (the user's primary session) with a spawn directive. State lives in files; the conductor reads board.json between turns. Loads on the swarm-supervisor invocation only — not invoked directly by the user.