event-debrief
SolidProduce a post-event recap after a conference, summit, or VIP engagement - contacts met, conversations, commitments, leads to log, and follow-up actions. Use after attending an event to capture outcomes before they decay. Trigger when the user says "event debrief", "post-event recap", or "debrief [event]". Feeds the orchestrator's Post-Event Follow-ups pattern when mass follow-ups are needed.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- mishahanin
- Repository
- mishahanin/heading-os
- Created
- 2 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
discovery-debrief
Structured debrief AFTER a customer conversation — extract learnings, update hypotheses, track demand signals. Use when the founder says "talked to a customer". For preparing and planning interviews beforehand, use conducting-user-interviews.
interview-debriefer
Turns one interview into structured notes within 24 hours, part of the Design Thinking Pack by Polar Bear. Use this whenever the user says "run interview-debriefer", "debrief this interview", "structure my interview notes", "here's the transcript from today's call", or an interview just ended and the notes are a wall of raw text. Use it even for "I just got off a user call".
debrief
Meeting and transcript processing — classifies meeting type, applies name corrections, extracts insights across 7 categories, generates protocols, proposes tasks with project field mapping. Checkpoint-based workflow. Supports full 8-phase flow (with GitHub reconciliation + distribution email) and quick 5-phase flow; `--all` and `--date YYYY-MM-DD` batch flags absorb the former /process-meeting. Trigger: "/debrief", "/debrief {path}", "/debrief --quick", "/debrief --all", "/debrief --date YYYY-MM-DD", "process meeting", "transcript processing", "create minutes", "process-meeting", "meeting minutes", "process transcript".