session-summary

A complete end-of-session summary is generated by coordinating all wrap-up tasks in a single pass, orchestrating sub-skills like session-outcomes and session-knowledge to produce a unified recap across projects.

Capturing session outcomes and syncing data is best handled by an orchestration workflow that verifies tool availability, extracts outcomes, and captures knowledge sequentially to present a consolidated end-of-session report.

Yes, a single orchestration command can extract knowledge and summarize outcomes across multiple projects by implementing sequential dependency ordering to validate tools and run all wrap-up tasks in one unified workflow.

No external dependencies or tool installations are required. The session wrap-up workflow validates tool availability internally and orchestrates its own sub-skills to coordinate the complete end-of-session report generation.

Sequential dependency ordering works by validating tool availability first, then chaining tasks like syncing sessions, extracting outcomes, and capturing knowledge to ensure each wrap-up step completes before producing the consolidated output.

A one-shot session wrap-up should be used at the end of any Copilot session when you need a unified summary for end-of-meeting reviews, avoiding the overhead of manually invoking individual skills for each wrap-up task.