skills.rest
KingSharkG
KingSharkGCOMMUNITY
Explore all skills by this author →
GitHub

post-task-review

Generate structured retrospective reports for completed tasks in ai-workflow-data.

Updated Apr 17, 2026
Search Tags:#audit#retrospective#orchestration#telemetry#quality-assurance#artifact#task-analysis
One-click install
npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill post-task-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-task-review
Source: https://github.com/KingSharkG/ai-agents-workflow/tree/main/skills/post-task-review
Command: npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill post-task-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a structured retrospective after a task completes, consolidating rework signals, artifact completeness, telemetry gaps, and user feedback prompts to guide future work.

Core Features & Use Cases

  • Append a comprehensive ## Retrospective section to the task-level summary.md by analyzing orchestration-state.json, per-subtask summaries, and telemetry data.
  • Produce a Rework Heat-Map and Artifact Completeness Audit to surface root causes and missing artifacts for each subtask.
  • Report Dispatch Bundle Coverage and telemetry gaps to close the loop with actionable improvements.

Quick Start

After a task reaches phase: complete, trigger this review to append the retrospective to the task summary.

Frequently Asked Questions about post-task-review

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

FAQPage Schema
How do I automate a post-task retrospective for completed workflow orchestration tasks?▼

Automate a post-task retrospective by triggering a review after a task reaches phase complete, which reads orchestration-state.json and per-subtask summaries to append a Retrospective section to the task summary.

Can I generate a rework heat-map and artifact completeness audit from orchestration telemetry?▼

Yes, generate a rework heat-map and artifact completeness audit by analyzing orchestration-state.json and telemetry data to surface root causes and identify missing artifacts for each subtask.

What is the best way to consolidate telemetry gaps and dispatch bundle coverage into a structured report?▼

Consolidate telemetry gaps and dispatch bundle coverage into a structured report by analyzing completed task telemetry data and appending the findings to the task-level summary.md file.

Does the post-task review process require a specific orchestration-state.json format to work?▼

The post-task review requires tasks tracked in ai-workflow-data to reach phase complete, reading the existing orchestration-state.json and summary.md files to generate the retrospective insights.

When should I not use an automated retrospective for task analysis?▼

Avoid running an automated retrospective before the task reaches phase complete, as the review depends on reading finalized orchestration-state.json and per-subtask summaries to generate accurate insights.

Why does my post-task retrospective fail to append to the task summary?▼

A post-task retrospective fails to append when the task has not reached phase complete or the required orchestration-state.json and summary.md files are missing from the tracked workflow data.

Related Skills

Explore More Data & Analytics Skills→
AtaraxiaEpiphanyAtaraxiaEpiphany

reconcile

Synchronize track-state.json with plan.md by mapping tasks via phase and name identifiers.

Community
Advanced
geekdesign27geekdesign27

bmad-retrospective

Automates team retrospectives for software development epics with a defined workflow.

Community
Advanced
jhillbhtjhillbht

data-audit

Audit Meta Ads accounts for performance gaps and tracking deficiencies.

Community
Advanced
CatsofsufferingCatsofsuffering
5

spec-fast

Coordinate OpenSpec workflow phases with Codex and bounded rework loops.

Community
Advanced