implementation-report

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.

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.

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.

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.

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.

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.