aget-report-progress

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

11|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/aget-framework/aget --skill aget-report-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aget-report-progress
Source: https://github.com/aget-framework/aget/tree/main/.claude/skills/aget-report-progress
Command: npx skills add https://github.com/aget-framework/aget --skill aget-report-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way to report on the progress of ongoing work, clearly identifying what has been completed, what is currently in progress, and any blockers or risks that may impede further progress. It also facilitates smooth handoffs by documenting the current state and next steps.

Core Features & Use Cases

  • Progress Assessment: Quantifies completion percentage and identifies remaining tasks.
  • Blocker Identification: Clearly flags any obstacles preventing task completion.
  • Risk Management: Highlights potential risks and suggests mitigation strategies.
  • Handoff Documentation: Prepares context and next steps for seamless continuation of work.
  • Use Case: A developer working on a feature can use this skill at the end of their workday to report their progress, mention any code merge conflicts they encountered, and outline what they plan to tackle tomorrow, ensuring their team lead has a clear understanding of the project status.

Quick Start

Use the aget-report-progress skill to report on the current status of the 'user authentication module' development.

Frequently Asked Questions about aget-report-progress

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

FAQPage Schema
What is a progress report and how does it help with project handoffs?

A progress report documents completion percentage, current blockers, and remaining items to facilitate project handoffs. It assesses current state, identifies issues, and prepares context for seamless continuation of work.

How do I report work progress and identify blockers for my current tasks?

To report work progress, assess the current state, calculate completion percentage, flag any blockers, and outline next steps. This structured process highlights potential risks and prepares handoff documentation for task continuation.

How do I document project risks and mitigation strategies during a handoff?

Document project risks and mitigation strategies by assessing the current state and highlighting potential issues that impede progress. This prepares handoff context with structured outputs for blockers and remaining items.

Can I use a structured format to report task status and completion percentage?

Yes, you can use structured output formats to report task status and completion percentage. This approach quantifies remaining tasks, flags obstacles, and prepares handoff details for ongoing work continuation.

What is the best way to manage risk and blockers when reporting project updates?

The best way to manage risk and blockers in project updates is to assess the current state, calculate progress, and clearly flag obstacles. This identifies issues and suggests mitigation strategies for smooth handoffs.

When do I need to generate handoff documentation for ongoing software engineering tasks?

You need to generate handoff documentation when transitioning ongoing software engineering tasks. It quantifies completion percentage, identifies blockers, and outlines remaining items to ensure seamless work continuation.