Push the right status to the right people so they stop asking "what's going on?"
Stakeholders often won't go look at the dashboard. This recipe creates targeted, push-based communication packets: snapshot status, confidence drivers, next decisions, and escalation asks. It also enforces a stakeholder comms plan — audience, cadence, channel, format.
Create a skill called "Stakeholder Pulse Push". Purpose: convert project state into role-specific, push-based updates that build confidence. When I provide project status (or raw notes), you will: - Create/refresh a stakeholder communication plan: audience tiers, cadence, channel, and format. - Produce an "Executive Pulse" update and a "Delivery Pulse" update. - Include decisions needed: decision, owner, deadline, impact if delayed. - Maintain an audit trail section I can paste into a comms log: date, audience, key changes. Guardrails: - No fluff; every line must answer "so what?" - Prefer push updates over asking stakeholders to click links. - If stakeholders' needs are unknown, ask 3 concise questions to infer them.
Provide your current project state (milestones, risks, blockers, decisions needed) and
this recipe segments your stakeholders by tier — exec, sponsor, functional lead, delivery —
then generates role-appropriate push updates. Executives get a tight RAG summary;
delivery leads get the working details.
Turn technical findings into language executives actually understand
Takes your technical analysis — complete with p-values, confidence intervals, and methodology caveats — and generates an executive-friendly version with clear takeaways, business implications, and recommended actions.
Convert "quick asks" into logged change requests with impact analysis and approvals
Scope creep is a margin killer and a schedule killer. This recipe creates a strict-but-practical change control loop: capture request, classify, analyze impact (time/cost/scope/risk), propose options, and route for approval. It keeps a change log so Slack decisions don't silently rewrite the project.
Stop being the family project manager
Build a weekly schedule, decision rules, and scripts that prevent one parent from becoming the household operations manager. Coverage grid, handoff protocol, and conflict-prevention rules included.
Set the rules before the resentment builds
Most roommate conflicts start with unspoken expectations. This skill generates a written agreement covering noise, guests, cleaning, and bills, plus a weekly check-in format and a conflict script for when things get tense.