Create session-based progress logs in append-only Markdown format.
npx skills add https://github.com/pjordan/claude-toolkit --skill progress-writing
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
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.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
steveclarkeResearch Todoist investigation tasks and append summaries to Obsidian daily notes.
mietheCreate, update, query, and validate YAML+Markdown tracking artifacts.
tduck1equackAutomate session recording and task archiving post-code commit with Python scripts.
shenxingyUpdate TODO.md and append session outcomes to PROGRESS.md from git history.
