bmad-spec: include event in memlog --type list
The documented append --type set omitted event while the next line requires --type event for terminal moments. Align the list.
This commit is contained in:
parent
6bb5cb3f61
commit
b522ce7def
|
|
@ -58,7 +58,7 @@ Deriving the contract from a living log instead of editing the contract in place
|
|||
Writes go through the shared script — `{project-root}/_bmad/scripts/memlog.py`, the same location as `resolve_customization.py` (atomic; never read it back except to resume):
|
||||
|
||||
- `python3 {project-root}/_bmad/scripts/memlog.py init --workspace {spec-folder} --field topic="<what is being specced>"` — once, at create.
|
||||
- `python3 {project-root}/_bmad/scripts/memlog.py append --workspace {spec-folder} --type <decision|constraint|capability|assumption|question|direction|note> --text "<one-line gist, reason included>"` — as each lands.
|
||||
- `python3 {project-root}/_bmad/scripts/memlog.py append --workspace {spec-folder} --type <decision|constraint|capability|assumption|question|direction|note|event> --text "<one-line gist, reason included>"` — as each lands.
|
||||
- Terminal moments (a validation verdict, "spec finalized") are `--type event` entries; the memlog carries no status field.
|
||||
|
||||
## The Operation
|
||||
|
|
|
|||
Loading…
Reference in New Issue