Progress Update Skill

Append structured progress entries to a per-project daily markdown file.

41|4|Updated May 6, 2026
One-click install
npx skills add https://github.com/markerikson/opencode-config-example --skill progress-update-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Progress Update Skill
Source: https://github.com/markerikson/opencode-config-example/tree/main/config/skill/progress-update
Command: npx skills add https://github.com/markerikson/opencode-config-example --skill progress-update-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of capturing what you completed in a work session reliably, without repeatedly reading and rewriting a growing daily progress file, which can cause context bloat and ordering issues.

Core Features & Use Cases

  • Session-end progress logging: Append timestamped entries at natural session boundaries (end of work, before switching tasks, after milestones).
  • Safe append workflow: Uses a dedicated devplans script to manage file mechanics, enforcing the rule to never read the progress file to append.
  • Structured entries: Produces a consistent format using JSON fields like slug, content, and optional nextSteps, including Next Steps replacement logic and auto-maintained Summary.

Quick Start

Ask your AI to record the end-of-session progress by first running devplans.ts progress to fetch the current tempFile and nextSteps, then composing a JSON entry with a slug and Markdown content, and finally appending it via devplans.ts progress append <tempFile>.

Frequently Asked Questions about Progress Update Skill

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

FAQPage Schema
How do I log daily progress updates in markdown without context bloat?

Daily progress updates are logged by appending structured JSON entries with timestamps and slug headings to a markdown file, avoiding file reads to prevent context bloat. This approach preserves chronological ordering and maintains Summary integrity.

What is the safe append workflow for session tracking in markdown?

The safe append workflow fetches write metadata and nextSteps via a dedicated devplans script, composes a JSON entry, and appends it to a tempFile. This enforces the rule to never read the progress file directly when appending entries.

Can I record multiple progress entries on the same day for different milestones?

Yes, multi-entry days are supported using timestamps and slug headings. Each end-of-session update or milestone wrap-up is appended chronologically as a separate structured entry, preserving the file's Summary and Next Steps sections.

Does appending progress logs require devplans to fetch next steps?

Yes, the workflow requires running devplans.ts progress to fetch the current tempFile and nextSteps before composing and appending the JSON entry. This ensures write metadata and next steps are correctly integrated into the daily log.

What are the limitations of automated workflow logging for daily dev plans?

The workflow relies on a dedicated devplans script for file mechanics and does not read the existing progress file during appends. It is designed for structured session tracking and may not suit workflows requiring in-place editing of previous historical entries.