incoming-request-advisor — Claude Code skill: decode a request

What incoming-request-advisor does

The skill puts the agent in a product leader's chair and works through an incoming message: a Slack ping, an email, a mandate, an escalation. It pulls the literal request apart from the job the sender is chasing, then returns a Markdown breakdown.

Its concepts are specific. The sender's role is read against your own work — upstream, peer or downstream — because the same words call for a different answer depending on who wrote them. Success criteria (how the result will be judged) stay separate from must-haves (what goes into the deliverable). Guesses are labelled as inferences and collected in a list of assumptions to validate.

The depth matches the message. A one-line ping does not get all twelve sections; empty ones are collapsed or marked as having nothing stated. Each bullet stays short and scannable, like a sticky note. When the sender or the situation is unclear and it changes the read, the skill asks at most three questions, one at a time, then continues on labelled assumptions. The message can arrive as text, a screenshot, an image or a file.