What problem does it solve? Stakeholder communication often fails because findings are vague, design decisions are defended with taste instead of evidence, and status updates bury the ask. This Skill turns finished research, designs, and project state into presentations and written updates that survive challenge because every claim is anchored to evidence. ## Core Features & Use Cases - Research readouts (Mode A): Structure findings with a 5-part anatomy (issue, evidence, severity, location, recommendation), small-N honest language (counts, not percentages), and video clip rules for skeptical audiences. - Design-rationale presentations (Mode B): Walk stakeholders through the decision path with named anchors (user evidence, data, principle, constraint) and a dissent-handling protocol that classifies pushback before responding. - Async BLUF updates (Mode C): Write bottom-line-up-front status messages with one ask, a by-when, and a 30-second read time. - Use Case: After a 5-participant usability test, produce a readout where each finding states the observed behavior, a count like "4 of 5 participants", a Nielsen severity rating, the exact screen location, and a recommendation — then send a BLUF update asking for fix approval by Friday. ## Quick Start Use the present-and-defend-work skill to turn my usability test findings into a stakeholder readout and a BLUF status update for the team.
