ck:journal

To write concise journal entries for recent code changes, you can use a lightweight skill to document important events and decisions in a structured format. It guides reflection on recent commits and experiments within your local workspace.

The best way to document engineering decisions is through reflective journaling in a structured local directory. This approach captures session insights and workflow events consistently without fragmenting your documentation across scattered files.

You should store session reflections and project journals in the ./docs/journals/ directory. This allows for easy reference during retrospectives and keeps your engineering documentation organized within your local workspace.

Yes, project documentation and journaling requires a SKILL.md file with YAML frontmatter containing the name and description. This structured format ensures consistency across your journal entries and reflective notes.

You can automate reflective journaling by asking the AI to summarize the latest changes and decisions. A journal-writer subagent guides the reflection process to ensure consistency across entries from recent commits and experiments.

The limitation of lightweight journaling is that it focuses strictly on concise entries rather than exhaustive documentation. It is designed for capturing recent changes and decisions, not replacing full project specifications or comprehensive wikis.