summarize-meeting

Structured meeting notes are generated by parsing command execution outputs from dashboard.md and results files, consolidating task statuses, key artifacts, decisions, and unresolved issues into a concise summary report.

The best way to summarize post-command analysis results is to consolidate task-specific result files and dashboard data into a coherent report, highlighting achievements, decisions made, and outstanding issues for clear reporting.

Yes, you can outline actionable next steps after a command execution. The skill provides concrete recommendations for future tasks and suggests the next logical command to run based on the structured summary.

The skill requires specific file formats to create a summary report, specifically parsing information structured within dashboard.md and task-specific result files like results/*.yaml to organize the output.

You consolidate task statuses and unresolved issues into a reporting overview by applying the skill to post-command workflows, which parses the raw execution data and structures it into a comprehensive overview.

Before generating a post-command summary, you need the raw execution outputs stored in dashboard.md and task-specific results/*.yaml files containing the task statuses, artifacts, decisions, and issues to parse.