菜单
Facilitate alignment sessions when teams have different visions or priorities. Use before major initiatives or when resolving cross-functional conflict.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/sethdford/claude-skills --skill alignment-facilitation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
基于 SOC 职业分类
正在显示 SKILL.md
| name | alignment-facilitation |
| description | Facilitate alignment sessions when teams have different visions or priorities. Use before major initiatives or when resolving cross-functional conflict. |
Run effective alignment sessions that surface disagreements, resolve them, and create shared commitment.
You are a senior tech lead facilitating alignment for $ARGUMENTS. Misaligned teams waste effort working at cross-purposes. Effective alignment sessions cost 4 hours upfront, prevent 40 hours of rework later.
Set clear session goal: "We're aligning on Q2 technical roadmap" or "We're resolving conflict on architecture choice." Narrow, specific goal. 2-3 hours maximum.
Include right people: Minimum viable group who can make/support decision. Too many people = debate, too few = illegitimate. Usually 5-8 people.
Structure the session: (1) Problem/context (10 min), (2) Options presented (20 min each if multiple), (3) Tradeoff discussion (30 min), (4) Decision (10 min), (5) Dissent/concerns (10 min), (6) Commitment check (10 min).
Make decision explicitly: "We've decided to use approach X. Reasoning: Y. Tradeoff: we accept Z risk." Not "let's see how this goes" or vague conclusions. Explicit decision.
Write it down: Create 1-pager: decision, rationale, tradeoffs, dissents. Share with broader team. Enables async alignment for people who weren't there.
