Skip to content

Team devlogs (weekly files)

Separate from the lead development log (Gabriel Li), which logs notable repo-wide changes chronologically.

Lead log front matter

Rephrased Wiki/DEVLOG.md uses the same metadata as other published wiki pages:

---
owner: Gabriel Li
status: stable
last-reviewed: YYYY-MM-DD
---

Update last-reviewed when the log is reviewed or reorganized, not for every new entry. The lead log does not carry a ## Change history section — dated entries are the history.

Use one ## YYYY-MM-DD section per calendar date. Combine same-day work into that single section instead of stacking duplicate date headers.

Markdown files physically live beside this README (Rephrased Wiki/wiki/devlogs/).

Naming and sidebar wiring

Use ISO week filenames below. First time you add a weekly log, also add a row under Engineering → Devlogs in mkdocs.yml (display name + file path). The coding agent can do that when you say the session is done; you can also edit the sidebar by hand.

Starter scaffolding is in _template.md (tracked in Git but omitted from MkDocs via exclude_docs).

One Markdown file per person per week (or negotiated sprint rhythm), named so merges stay collision-free.

Convention: YYYY-Www-FirstName.md (ISO week), e.g. 2026-W19-Alice.md

Example: 2026-W21-Alex.md — sample weekly file and MkDocs sidebar wiring for a fictional engineer.

Optional front matter at the top of each file:

---
author: FirstName
week: 2026-W19
---

Keep entries short: what shipped, what blocked, what you need from leads or other disciplines.

Change history

  • 2026-08-13 — Gabriel Li — Weekly logs: ISO names + mkdocs.yml; dropped named-skill prompt.
  • 2026-05-23 — Gabriel Li — Example weekly devlog 2026-W21-Alex.md and MkDocs sidebar entry; lead DEVLOG front matter and one-section-per-date rule documented.
  • 2026-05-09 — Gabriel Li — Documented sidebar workflow, _template.md, and devlog-entry prompts.
  • 2026-05-08 — Gabriel Li — Added baseline change history section for weekly wiki maintenance.