skills.rest
github
githubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

desk-journal

Write, append, and read persistent journal entries that preserve work context across sessions.

38.5k|4.9k|Updated Jun 11, 2025
Search Tags:#context tracking#journal#Markdown#workflow continuity#persistent memory#Session Handoff
One-click install
npx skills add https://github.com/github/awesome-copilot --skill desk-journal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desk-journal
Source: https://github.com/github/awesome-copilot/tree/main/skills/desk-journal
Command: npx skills add https://github.com/github/awesome-copilot --skill desk-journal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI sessions start from zero context, so progress, decisions, and dead ends are lost when a session ends. This Skill maintains a persistent journal per desk so the next session can pick up exactly where the last one stopped.

Core Features & Use Cases

  • Session Handoff Entries: Append structured entries recording what was done, current state, and the next step to desks/<desk-name>/journal.md.
  • Session Startup Recovery: Read the journal at the start of a session to restore context, with the most recent entry carrying the current state and next step.
  • Desk Closure Summaries: Write a final wind-down entry capturing overall accomplishments, artifacts left on the bench, and handoff notes when a desk closes.
  • Use Case: After a long debugging session, record which repositories were scanned, what findings were triaged, and what the next session should investigate, so no work is repeated.

Quick Start

Write a journal entry for the current desk summarizing what was done, the current state, and the next step.

Frequently Asked Questions about desk-journal

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

FAQPage Schema
How do I preserve context between AI sessions?▼

Append a structured journal entry to the desk's journal.md file at the end of each session. Each entry records what was done, the current state, and the next step, so the next session can resume without re-deriving context.

What should a good journal entry include?▼

A good entry has three parts: what was worked on, the current state, and the next step. Keep it to 3-5 lines, be specific about results, and include dead ends so the next session avoids repeating them.

Where are desk journal entries stored?▼

Entries are appended to desks/<desk-name>/journal.md as Markdown sections. Each section is headed by a date and short summary, followed by bullet points for worked-on items, current state, and next step.

When should I write a journal entry?▼

Write entries at the end of a session, at the start when reading prior context, at mid-session checkpoints after significant progress, and as a final summary when a desk is being closed.

What is the difference between a session entry and a desk closure entry?▼

A session entry captures progress and the next step for continuation. A desk closure entry summarizes what the desk accomplished overall, lists artifacts left on the bench, and notes any handoff information for other desks or the operator.

Related Skills

Explore More Software Engineering Skills→
zhukunpenglinyutongzhukunpenglinyutong
3.9k

record-session

Record coding session summaries and commit hashes into Trellis journal files.

Community
Advanced
liminalwarmthliminalwarmth
2

sdv-session-start

Gather context from journals, git state, and build status to orient development sessions.

Community
Intermediate
emilneuraz-aiemilneuraz-ai

context-driven-development

Create and maintain conductor context artifacts like product.md and workflow.md.

Community
Advanced
LevNasLevNas
3

plan-task

Persist multi-step plans and task progress across coding sessions.

Community
Advanced