devlog
- Group: Documentation
- When it activates: Finishing a relevant step or committing (always); questions about the project’s past (memory and search)
- Installed: Always: comes with every project.
Documents the work in senzu/devlog/ at the project root following the team’s methodology.
When to use
Section titled “When to use”- Before every
git commit. - When finishing a relevant step/feature/fix.
- When an entry corrects or improves a previous one.
Project with its own diary
Section titled “Project with its own diary”If the project already documents things its own way (CHANGELOG.md, docs/decisions/, ADRs) and no decision has
been made yet: ask the user ONCE what they prefer (their format, this devlog, or both with different roles),
write the decision in the first entry (or in their diary) and respect it for the rest of the project without asking again.
- Determine the real date:
Get-Date -Format 'yyyy-MM-dd HH:mm'. - Make sure the day’s folder exists:
senzu/devlog/<YYYY-MM-DD>/. - Compute the next GLOBAL sequential number by reading the highest existing
NNNin all ofsenzu/devlog/**and adding 1 (3-digit format:001,002…). - Create
senzu/devlog/<date>/NNN-<slug>.mdwith the entry template. - If this entry improves/corrects another one, fill in
Mejora a: NNN(improves). - Record the step’s commits (short hash + message).
- If there were decisions, add them to
senzu/devlog/<date>/DECISIONES.mdand tosenzu/devlog/MEMORIA.mdas current (D-xxx · decision and why · ver NNN); if they replace another one, mark it as replaced (references/memoria.md). - Update
senzu/devlog/INDEX.md(table: no., date, title, type, improves, task). - If the entry closes a card in
senzu/plan/PLAN.md, fill inTarea: <id>(task) and put the entry’s path in the card’sDevlog:field when marking itdone.
Memory and searching the past
Section titled “Memory and searching the past”| I need… | Do |
|---|---|
| To know what is decided | senzu/devlog/MEMORIA.md (it reaches you at session start). Do not contradict it without citing it and asking. |
| Something that is not in the memory («why…?», «when did we change…?») | node <skills-dir>/devlog/scripts/buscar.mjs "words" → open ONLY the indicated entry, by section |
| To create the memory in a project with history | references/memoria.md § Crear la memoria desde un devlog existente (create the memory from an existing devlog) |
| Memory longer than 60 lines | Move what was replaced or closed to senzu/devlog/MEMORIA-historico.md |
| The user gives a rule or a correction («don’t ever…», «from now on…») | /remember: to the project (MEMORIA.md) or to their personal memory if it applies to all their projects (references/memoria.md §7) |
| Resume the previous session | /resume (references/memoria.md §8) |
| Review the memory (expired, broken «ver NNN», repeated D) | node <skills-dir>/devlog/scripts/memoria-check.mjs |
When answering about the past, cite the entry (according to 034…). If the search finds nothing after
trying synonyms, say so: «nothing is recorded about this». Never assume it.
Entry template
Section titled “Entry template”See this skill’s templates/devlog-day.md. Minimum fields:
# NNN — title, Fecha/hora (date/time), Tipo (type), Mejora a (improves), Tarea (task: F1-T2 | X-T1 | —), Stack, Qué se hizo (what was done),
Commits, Decisiones (decisions), Verificación (verification), Próximos pasos (next steps).
Phase summary
Section titled “Phase summary”When a phase of senzu/plan/PLAN.md is closed, write a normal entry of type docs (same template
and numbering; Tarea: with the id of the closing card if there is one) with: what was delivered and how the
user verifies it step by step, links to the entries of each task in the phase, global
verification (suite, CI) and a short retro (what to keep, what to change). It is linked from the closing
card and from the phase’s row in ## Fases.
- Global sequential numbering; it does not restart each day.
- Never invent the date; use the system’s.
- At least one
.mdper day; if the day is very long, several.md.