incoming-request-advisor

Decode incoming messages into structured breakdowns separating literal asks from underlying jobs-to-be-done.

6.8k|818|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill incoming-request-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incoming-request-advisor
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/incoming-request-advisor
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill incoming-request-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about incoming-request-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a vague stakeholder request before responding?

Paste the message into the incoming-request-advisor, which renders a twelve-section breakdown covering the literal ask, underlying problem space, sender read, constraints, and risks. It then offers four next moves including drafting a reply or counter-proposal.

How to separate a feature request from the actual job-to-be-done?

The breakdown's Section 4 explicitly names the outcome and job behind the request, distinct from Section 3's literal ask. Every inferred motive is labeled as an assumption to validate rather than presented as fact.

Can I use this with screenshots or attached files of messages?

Yes, the Skill extracts the full message from pasted text, screenshots, images, attached files, or PDFs before analyzing. If any part is unreadable or cut off, it says so and works with what is available.

What happens if I only paste the message with no context?

The advisor asks at most three targeted questions, one at a time, about sender identity, situation, and desired output, then proceeds with clearly labeled assumptions. It never re-asks anything the message already answers.

When should I not use a full message breakdown?

For trivial one-line FYIs, the Skill collapses empty sections and marks them 'none stated' rather than rendering all twelve sections. Over-filling a short message is treated as a failure mode, not thoroughness.