journal

Create structured post-mortem and retrospective journal entries in .workbench/journals or plans/journals.

5|Updated May 2, 2026

Search Tags:#retrospective #post-mortem #engineering #journal #workflows #log #incident

Ready to run

npx skills add https://github.com/vanducng/skills --skill journal-vanducng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: journal
Source: https://github.com/vanducng/skills/tree/main/skills/journal
Command: npx skills add https://github.com/vanducng/skills --skill journal-vanducng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write focused engineering journal entries to capture retrospective notes after shipping or post-mortems on incidents, ensuring context is preserved for future work.

Core Features & Use Cases

Records concise, structured post-mortem and retrospective entries after releases, incidents, or debugging sessions.
Stores entries in .workbench/journals/ when the project migrates, or plans/journals/ for legacy projects.
Enforces one-entry-per-event and provides templated formats for retro and incident contexts.

Quick Start

Run vd journal after a ship, cook, or incident to create a new focused entry in the appropriate journals directory.

Frequently Asked Questions about journal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write a post-mortem for an engineering incident?▼

To write a post-mortem for an engineering incident, use mode-aware templates to create a single structured entry with required frontmatter. This preserves failure context immediately after debugging or a release.

What is the best way to capture retrospective notes after a ship?▼

Capturing retrospective notes after a ship requires a single-entry log with structured frontmatter. It records concise engineering context immediately following a release or debugging session.

How do I log engineering workflows and incidents in my project?▼

You log engineering workflows and incidents by creating a focused entry in the project's journals directory. It enforces one-entry-per-event discipline using mode-aware templates for retro and incident contexts.

Where are engineering retrospective entries stored?▼

Engineering retrospective entries are stored in .workbench/journals for migrated projects or plans/journals for legacy projects. This ensures post-mortem and retrospective logs are persisted correctly.

Does the journal log enforce a specific format for incident entries?▼

Yes, the incident log enforces a specific format requiring structured frontmatter and one-entry-per-event discipline. Mode-aware templates differentiate retrospective entries from incident post-mortems.

When should I not use a single-entry log for post-mortems?▼

You should not use a single-entry log for post-mortems if you need multiple entries per incident or lack structured frontmatter. The system enforces one-entry-per-event discipline for focused context.