implementation-report

Generate a structured implementation report after completing a software subtask.

Updated Apr 17, 2026

Search Tags:#implementation #audit #telemetry #report #subtask #ai-workflow

Ready to run

npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill implementation-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-report
Source: https://github.com/KingSharkG/ai-agents-workflow/tree/main/skills/implementation-report
Command: npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill implementation-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produce this report immediately after completing a subtask. Record everything that happened — do not summarize or omit failures.

Core Features & Use Cases

Generate a detailed implementation report right after task completion that captures metadata, changes, and diagnostic data.
Support a standardized Output Template with sections for metadata, summary of changes, files changed, tests run, dynamic skills used, plugins used, unresolved issues, and a project state update.
Handle ultra-light path scenarios by guiding placement of the impl-ultra block in the output template and avoiding duplication in the main report.

Quick Start

Run the Implementation Report Skill immediately after completing a subtask to generate and append the detailed report.

Frequently Asked Questions about implementation-report

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

FAQPage Schema

How do I automatically generate a post-task implementation report for software development workflows?▼

Automatically generate a post-task implementation report by running the Skill immediately after completing a subtask. It produces a standardized template capturing metadata, summary, files changed, tests run, and project state.

What should be included in a post-execution implementation report for change tracking?▼

A post-execution implementation report should include metadata, a summary of changes, files changed, tests run, dynamic skills used, plugins used, unresolved issues, and a project state update to ensure comprehensive telemetry and change tracking.

How do I document unresolved issues and diagnostic data after completing a subtask?▼

Document unresolved issues and diagnostic data after completing a subtask by generating a structured implementation report. This records everything that happened during execution without summarizing or omitting failures.

Can I use this implementation report generation approach for both frontend and backend tasks?▼

Yes, this implementation report generation approach supports software development workflows across both frontend and backend tasks. It applies a consistent output template to capture telemetry and changes for any subtask type.

How do I handle ultra-light path scenarios when generating an implementation report?▼

Handle ultra-light path scenarios by guiding the placement of the impl-ultra block within the output template. This avoids duplication in the main report while maintaining a standardized documentation structure.

What is the best way to ensure consistent documentation across multiple completed subtasks?▼

The best way to ensure consistent documentation across subtasks is to apply a standardized output template. This enforces uniform sections for metadata, change tracking, telemetry, and unresolved issues immediately after execution.