alignment-action

Summarize stakeholder disagreements, list assumptions, and assign owners.

37|5|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/BellaBe/lean-os --skill alignment-action
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alignment-action
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/action-alignment
Command: npx skills add https://github.com/BellaBe/lean-os --skill alignment-action

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Highlights and resolves conflicts around requirements and ownership.

Core Features & Use Cases

  • Situation summary: Gathers disagreement points.
  • Explicit assumptions: Lists what is assumed.
  • Actionable decisions: Proposes owners and next steps.

Quick Start

Provide a disagreement summary; returns structured alignment outputs.

Frequently Asked Questions about alignment-action

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

FAQPage Schema
How do I resolve conflicts and misalignment among stakeholders?

Resolving stakeholder conflicts involves surfacing disagreement points, listing explicit assumptions each party holds, identifying the core conflicts, and assigning clear owners to decisions. This Skill structures that process by creating a situation summary, assumption inventory, and actionable next steps to clarify ownership and move forward.

What's the best way to handle unclear requirements and ownership confusion?

Unclear requirements and ownership confusion stem from unstated assumptions. The alignment-action approach documents the current disagreement, makes assumptions explicit, isolates which decisions are blocking progress, and assigns owners to each decision. This transforms ambiguity into a structured, actionable plan.

How do I document and track stakeholder disagreements?

Document stakeholder disagreement by summarizing each party's position, listing what each assumes to be true, identifying where those assumptions conflict, and naming the specific decisions needed to resolve each conflict. Assign an owner to each decision. This creates a living reference that prevents re-litigation of settled points.

Can I use this approach for cross-functional requirement disputes?

Yes. Alignment-action works across any context where multiple stakeholders hold conflicting views on requirements or ownership. It surfaces hidden assumptions, isolates decision points that are genuinely contested, and creates explicit ownership so disputes do not resurface in later work phases.

What happens if stakeholders won't agree on next steps?

If agreement is not reached, the process still produces value: a documented summary of disagreement, each party's explicit assumptions, the specific conflicts blocking progress, and clarity on which decisions require escalation or additional input. This prevents stalled work and clarifies what information or authority is needed to move forward.