skills.rest
MaiconGambini
MaiconGambiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-progress-log

Updates harness progress files while preserving blockers and decisions.

Updated Jul 29, 2026
Search Tags:#documentation#markdown#state management#agent workflow#progress tracking#session continuity#harness
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-progress-log-maicongambini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-progress-log
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-progress-log
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-progress-log-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running agent workflows lose context between sessions when progress notes are scattered or overwritten. This Skill standardizes how progress files are updated so blockers, decisions, and verification status survive across sessions. ## Core Features & Use Cases - File Priority Resolution: Locates the active progress file by checking .specs/project/STATE.md, then docs/harness/progress.md, then agent-progress.md. - Structured Sections: Enforces required sections including Current Active Work, Verification Status, Blockers, Decisions Log, and Next Best Action. - Preservation Rules: Appends dated decisions, keeps existing blockers, and records verification as actual command output or an explicit not-run reason. - Use Case: After finishing a coding task in a multi-session harness workflow, update the project progress file so a fresh session can resume without re-reading the entire history. ## Quick Start Update the project progress file with the current work status, verification results, and next action while preserving existing blockers and decisions.

Frequently Asked Questions about harness-progress-log

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

FAQPage Schema
How do I update a project progress file without losing blockers?▼

Update progress by appending new information while preserving existing Blockers and Decisions Log sections. Add new decisions with a date and reason, and record verification as actual command output or an explicit not-run reason.

Which progress file should I use for harness workflows?▼

Check files in priority order: `.specs/project/STATE.md` first, then `docs/harness/progress.md`, then `agent-progress.md`. If none exists, propose creating `docs/harness/progress.md` and wait for approval before writing.

What sections should a progress file contain?▼

A progress file should include Current Active Work, Verification Status, Blockers, Decisions Log, and Next Best Action. These sections let a fresh session resume work without re-reading prior conversation history.

Can I create a new progress file automatically?▼

No. Creating a new progress file requires explicit approval. Before writing, output the target file, sections present and missing, the proposed update, and whether approval is needed.

How should verification status be recorded in progress logs?▼

Record verification as the actual command output that was run, or an explicit reason why it was not run. If work is blocked, include the exact failing command or missing dependency.

Related Skills

Explore More Software Engineering Skills→
aget-frameworkaget-framework
11

aget-report-progress

Reports progress completion percentage, blockers, risks, and remaining items for handoff documentation.

Official
Intermediate
ricky-yoshricky-yosh

bf-resume

Reload ticket context from brownfield-progress files and git history.

Community
Intermediate
the-agency-aithe-agency-ai
39

compact-prepare

Create structured session handoff files for multi-agent workflow compaction.

Official
Intermediate
h4vzzh4vzz
33

Project Management

Create and manage software project plans with task breakdowns and status reports.

Community
Advanced