progress-writing

Create session-based progress logs in append-only Markdown format.

Updated Aug 27, 2026

Search Tags:#workflow #documentation #handoff #notes #session-logs #progress-writing

Ready to run

npx skills add https://github.com/pjordan/claude-toolkit --skill progress-writing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: progress-writing
Source: https://github.com/pjordan/claude-toolkit/tree/main/skills/examples/progress-writing
Command: npx skills add https://github.com/pjordan/claude-toolkit --skill progress-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Progress files provide a durable, session-by-session record of work state that enables seamless handoffs, continuity, and auditability across agents, breaks, and context windows.

Core Features & Use Cases

Append-only session logs: Each work session creates a separate progress file with a clear header, summary, work log, test results, and handoff notes.
Blocker capture and handoff: Documents blockers, decisions, and next steps to ensure smooth continuation.
Use Case: Teams working on long-running features can hand off effort between agents with minimal loss of context and reproducibility.

Quick Start

Use the progress-writing skill to create a new session file for your feature progress, example: progress/session-001.md, and populate with a header and sections.

Frequently Asked Questions about progress-writing

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

FAQPage Schema

How do I write session logs for work handoffs across multiple agents?▼

Session logs for work handoffs use an append-only Markdown format containing a header, summary, work log, test results, issues, and next steps to ensure continuity across agents. Each session creates a separate progress file with zero-drift numbering and artifact links.

What is the best way to document blockers and next steps for long-running features?▼

Documenting blockers and next steps for long-running features requires structured progress files that capture decisions, test results, and handoff notes in an append-only format. This creates a durable, session-by-session record enabling seamless continuation and auditability across context windows.

Can I use Markdown progress files to track work state across context windows?▼

Markdown progress files track work state across context windows by applying an append-only structure with headers, summaries, work logs, test results, issues, and handoff notes. Zero-drift session numbering and artifact links maintain reproducibility and continuity across breaks.

Does session progress documentation work for resuming work after breaks?▼

Session progress documentation works for resuming work after breaks by providing a durable record of previous work state, captured blockers, and handoff notes. The append-only Markdown format with next steps sections ensures minimal context loss when continuing long-running efforts.

What should a session progress log include for seamless agent handoffs?▼

A session progress log for seamless agent handoffs includes a header, summary, work log, test results, issues, handoff notes, and next steps. It uses zero-drift session numbering and links to related artifacts to maintain reproducibility and minimal context loss across agents.

When do I need append-only progress files for documentation?▼

Append-only progress files for documentation are needed when teams work on long-running features requiring handoffs between agents, breaks, or context windows. They provide auditability and continuity by capturing session-by-session work state, blockers, and decisions in a durable format.