progress_reporting

Enforce standardized progress report structure and content across project agents.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/tardyp/esp_tock --skill progress-reporting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: progress_reporting
Source: https://github.com/tardyp/esp_tock/tree/main/.opencode/skills/progress_reporting
Command: npx skills add https://github.com/tardyp/esp_tock --skill progress-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized format and convention for progress reports, ensuring clarity, traceability, and efficient handoffs between agents in a project.

Core Features & Use Cases

  • Standardized Report Structure: Ensures all reports follow a consistent template for easy reading and comparison.
  • Agent-Specific Sections: Tailors reporting requirements for different roles (Analyst, Implementor, Integrator, Reviewer).
  • Handoff Documentation: Emphasizes the importance of clear handoff notes for seamless project continuation.
  • Use Case: An implementor finishes a coding task and needs to report progress. They use this Skill to generate a report detailing work completed, TDD metrics, and any issues encountered, ensuring the next agent has all necessary context.

Quick Start

Use the progress_reporting skill to create a new report for the current session.

Frequently Asked Questions about progress_reporting

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

FAQPage Schema
How do I standardize project progress reporting for multiple agents?

Standardizing project progress reporting involves enforcing a consistent report structure, location conventions, and agent-specific content requirements. This ensures clarity, traceability, and efficient handoffs between different project agents.

What is the best way to document handoffs for seamless project continuation?

The best way to document handoffs is to use a standardized reporting methodology that specifies mandatory elements like session summaries, work completed, findings, issues, and next steps. This ensures the next agent has all necessary context.

How does agent-specific reporting work for different project roles?

Agent-specific reporting tailors content requirements based on the agent's role, such as Analyst, Implementor, Integrator, or Reviewer. This means an Implementor reports TDD metrics and work completed, while other roles focus on their specific findings.

Can I use a standardized report structure for my project management methodology?

Yes, you can enforce a standardized report structure across all agents within a project. This enforces consistent templates for easy reading, comparison, and effective communication, directly aligning with structured project management methodologies.

When do I need standardized progress reporting in a project?

You need standardized progress reporting when multiple agents work on a project and require clear traceability. It is essential when an agent finishes a task and must communicate work completed, issues encountered, and next steps for effective handoff.