Menú
How to write the JOURNAL.md. Invoke when recording a finding, or a small decision worth keeping.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
What to expose in settings surfaces and how to organize it. Invoke before exposing a setting, organizing a page, or reworking a settings surface.
Testing posture — test behavior not implementation, stay sober, grow coverage per workstream. Invoke before writing a test or extending coverage.
One normalized way to name files, folders, symbols, resources and providers. Invoke before naming or renaming.
What to observe in code, and how to write it readable and actionable. Invoke before adding or changing an observation point.
How versions are numbered and the changelog written. Invoke before cutting a version, writing a CHANGELOG entry, or drafting release notes.
Commit grain and the few deviations from the universal convention. Invoke before committing, splitting a workstream into commits, or auditing history.
| name | deckle-journal |
| description | How to write the JOURNAL.md. Invoke when recording a finding, or a small decision worth keeping. |
| type | skill |
A diary: the small findings worth keeping, often surfaced while researching. The chronicle of what matters.
Record only what was found or decided. State it plainly — "found X", "chose Y because Z" — and stop. No inference, no deduction, no extrapolation beyond the bare fact: anything more misleads the next agent that reads it.
JOURNAL.md holds durable module findings — a measured API fact, a frozen decision, a trap worth the next agent's time. It is NOT the session work-log. The why of each action you took this session, and the handoff state, go to an Anytype rapport (session_start then log, anchored to the module's task), never here. If you are narrating what you did rather than recording a lasting fact, it belongs in the rapport.
