Skip to main content
ClaudeWave
Slash Command292 estrellas del repoactualizado 2d ago

workflow-stakeholder-alignment

The Stakeholder Alignment workflow guides users through a four-step process to build executive buy-in for a product initiative. It sequences stakeholder mapping, problem framing, solution development, and launch planning into cohesive artifacts that demonstrate both strategic alignment and execution readiness before committing organizational resources.

Instalar en Claude Code
Copiar
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/product-on-purpose/pm-skills/HEAD/commands/workflow-stakeholder-alignment.md -o ~/.claude/commands/workflow-stakeholder-alignment.md
Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

workflow-stakeholder-alignment.md

Run the Stakeholder Alignment workflow to build a compelling case for leadership buy-in before committing resources.

This workflow uses multiple skills in sequence. For each step, read the skill instructions and follow them to create the artifact.

## Workflow Steps

### Step 1: Stakeholder Summary

Use the `discover-stakeholder-summary` skill from `skills/discover-stakeholder-summary/SKILL.md`.

Map stakeholders, their priorities, concerns, and decision-making criteria.

### Step 2: Problem Statement

Use the `define-problem-statement` skill from `skills/define-problem-statement/SKILL.md`.

Frame the problem in terms that resonate with your stakeholder audience.

### Step 3: Solution Brief

Use the `develop-solution-brief` skill from `skills/develop-solution-brief/SKILL.md`.

Propose a solution in a concise, executive-ready format.

### Step 4: Launch Checklist

Use the `deliver-launch-checklist` skill from `skills/deliver-launch-checklist/SKILL.md`.

Demonstrate execution readiness with a comprehensive launch plan.

## Output

Create all four artifacts in sequence, ensuring each builds on the previous.

Reference the Stakeholder Alignment workflow at `_workflows/stakeholder-alignment.md` for additional guidance.

Context from user: $ARGUMENTS