synopsis_skill

Overview

This skill generates a manager-focused synopsis that summarizes what is happening now and recent work, always including an export (Save) button. It produces a compact HTML synopsis with a Current Context box, a Hero section showing the most recent completed task, and tabs for What Changed, Why It Matters, and Technical details. The output is designed to be saved directly into the project folder for easy distribution.

How this skill works

The skill inspects the current session context, recent conversation history, and the latest VCS activity to populate the synopsis sections. It then emits a complete HTML template that includes a blue Current Context box, a Hero block for the last completed task, tabbed sections for plain-language changes and technical notes, and an orange Save button wired to exportSynopsis(). The generated HTML replaces placeholders like [PROJECT_PATH] and all other markers with live content before output.

When to use it

• At the end of a focused work session to create a one-page manager summary
• When you need a quick, shareable snapshot of recent changes and next steps
• Before handoff or status meetings to capture immediate context and impact
• To export persistent records of session outcomes into the project folder
• When a stakeholder asks 'what changed and why it matters' in plain language

Best practices

• Always confirm Current Context describes what is happening right now (task, goal, next step)
• Populate the Hero with the most recently completed task and a one-sentence summary
• Replace [PROJECT_PATH] with the actual filesystem path so exportSynopsis() can save
• Include clear, plain-English bullet points in 'What Changed' and 'Why It Matters'
• Keep technical details concise: files modified, root cause, and the fix approach

Example use cases

• Generate a one-page summary after finishing a bugfix and save it to the project for reviewers
• Create a session snapshot before a demo so managers see what was completed and why it matters
• Produce a handoff synopsis when shifting work between team members
• Archive sprint checkpoints by exporting synopses into the project synopses folder
• Use the synopsis as a persistent record for audits or postmortems