tl-project-records
Installation
SKILL.md
tl-project-records
Three records, each answering one question, and the wiring that keeps them current without a separate chore.
| Record | Answers | Written | Reference |
|---|---|---|---|
DEVLOG.md |
What happened, when, and why? | Close-out, release, incident, ADR-producing decision, or on request | references/devlog.md |
docs/adr/NNNN-*.md |
Why is the project shaped this way? | When a change meets the trigger rule in docs/adr/README.md |
references/adr.md |
CHANGELOG.md |
What did each release change? | Rendered at release by changelog-cut; never hand-edited |
references/changelog.md |
Commit subjects feed the changelog, so they follow one rule (references/commit-subjects.md). One script, scripts/project-records.ps1, enforces every mechanical rule and renders the changelog (references/tool-contract.md).