Markdown workbench starter pack

Keep a record that still makes sense after the meeting or review is over. These plain-text templates separate what happened, what was decided and what someone needs to do next. They work in a Markdown editor or an ordinary text editor.

Choose the right note

Use the meeting note for discussion and follow-ups. Use the decision log when someone will later ask why you chose one option over another. Use the technical review to keep source links and checks beside your conclusion. Do not fill every field if it adds no useful information.

Save a copy with a meaningful name, write the next action and reopen the saved file to check where it went. Keep private material in an appropriate location; a synced folder may share it beyond this computer.

A short follow-up

# Follow up

Ask Morgan for the revised delivery date.

A technical review

# Parser review

## Source

- [Git diff reference](https://git-scm.com/docs/git-diff)

## Check before accepting

- [ ] Read the changed file.
- [ ] Run the relevant project check.

> Keep existing changes that belong to other work.

```bash
git diff --stat
```

Checkboxes record your own review. They are not proof that a command ran or a test passed.