justin/pm-claude-skills

Files

T

mohitagw15856 036511ab3e Windsurf + Aider targets, MCP server, and demo placement (#33 )

Broadens both reach (more tools) and content types (an MCP server), continuing
the multi-platform story.

Windsurf + Aider:
- build-exports.mjs gains two platforms: exports/windsurf/*.md (workspace rules,
  trigger: model_decision) and exports/aider/*.md (conventions for `aider --read`).
  Now 5 platforms (ChatGPT, Gemini, Cursor, Windsurf, Aider).
- install.sh + bin/cli.mjs install both (windsurf -> .windsurf/rules, aider ->
  .aider/skills with a --read hint); generated README index is excluded from copies.
- One-line windsurf-install.sh / aider-install.sh wrappers for parity.

MCP server (new content type):
- mcp/server.mjs — zero-dependency stdio MCP server exposing list_skills,
  search_skills, get_skill. Published as a second bin (pm-claude-skills-mcp).
  Logs to stderr; reads bundled skills/ at startup. mcp/README.md documents
  client config.

Also: README hero "See it in action" demo placement (ready to swap in a GIF;
recording guide in web/docs-assets/README.md), Works-With table + exports +
install docs updated, CHANGELOG Unreleased. package.json files/bin updated.


Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px

Co-authored-by: Claude <noreply@anthropic.com>

2026-06-17 23:15:38 +01:00

3.4 KiB

Raw Blame History

trigger, description

trigger	description
model_decision	Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.

Executive Update Skill

Produce a stakeholder update that busy executives will actually read — structured around what they care about: decisions, risks, and numbers.

Required Inputs

Ask the user for these if not provided:

Product update or notes (raw input to transform — even bullet points work)
Audience (CEO, board, specific exec, or general leadership)
Period (this week / sprint / month / quarter)
Key metrics (what numbers matter to this audience)

Executive Communication Principles

Lead with the headline, not the context
Every update should answer: "So what does this mean for the business?"
Flag decisions needed clearly — don't bury asks in paragraphs
Be honest about risks — executives hate surprises more than bad news

Process

Read the full product update provided
Identify: key metric movements, decisions required, risks to flag, wins to celebrate
Write in reverse pyramid style — most important first
Limit to 250 words maximum for the main body
Add a "Decisions Needed" section with clear options and your recommendation
Validate — Confirm every decision needed has a specific option and recommendation (not just "TBD"), and every risk has a mitigation or watch plan

Output Structure

Product Update — [Date / Sprint / Month]

Headline: [One sentence on the most important thing]

By the Numbers:

Progress This Period: [3-4 bullet points, outcome-focused not activity-focused]

Risks & Watch Items: [2-3 bullets — be direct, include mitigation]

Decisions Needed:

[Decision] — Options: [A] or [B] — Recommendation: [your view] — Needed by: [date]

What's Next: [2-3 bullets on next period priorities]

Quality Checks

Whole update is under 250 words (if not, cut ruthlessly)
Every metric includes a comparison point (vs. target or last period)
Every risk has a mitigation or watch action
Every decision needed has at least two options and a recommendation
Written for a CFO or CEO — no jargon, all outcomes

Anti-Patterns

Do not lead with context or background — executives read the headline first; bury the important thing below two sentences of setup and they will miss it
Do not present metrics without a comparison point — a number without context (vs. target, vs. last period) cannot be interpreted and will prompt follow-up questions
Do not soften or spin risks — executives rely on these updates to make resource and escalation decisions; sanitised risk sections destroy the update's utility
Do not present a "Decisions Needed" item without a recommendation — asking an executive to decide without your view forces them to do the analytical work the PM should have done
Do not exceed 250 words in the main body — length signals the author has not done the compression work; every word over 250 reduces the chance the update is read