What problem does it solve?
When a loaded Slack ping, email, mandate, or escalation lands, PMs often reply to the literal words and miss the outcome the sender actually wants. This Skill slows that reflex down by producing a structured breakdown of any incoming message before you respond.
Core Features & Use Cases
- Ask vs. Job-to-Be-Done Separation: Distinguishes the literal request from the outcome the sender is actually chasing, so you solve the right problem.
- Sender Read: Analyzes who sent the message, their role (upstream, peer, downstream), power, stake, sentiment, and subtext.
- Twelve-Section Breakdown: Covers classification, must-haves vs. success criteria, hard negatives, constraints, gaps, risks, and recommended next steps, scaling depth to the message length.
- Use Case: Your VP Slacks "can we get the dashboard redesign into next sprint? Board's asking." The Skill surfaces that the real job is board-ready proof of responsiveness, then offers to draft a reply, meeting agenda, discovery reframe, or counter-proposal.
Quick Start
Paste the incoming message you received and ask the incoming-request-advisor to break it down before you reply.