90天执行计划

解决什么问题

许多决策在“已决定”和“下周一做什么”之间夭折。团队记录了一份批准的决策，却缺乏将承诺转化为具体行动的结构化流程，导致进度失控、责任模糊、关键节点无人跟进。本技能填补这一断层：将一份决策文档扩展为可执行的 90 天路线图，明确谁负责、何时交付、按什么节奏检查。

核心能力与工作流

技能接收已批准的决策记录（如 /cs:decide 的输出），执行以下步骤：

• 分解工作流：将选定方案拆解为 3–6 个并行工作流，确保范围可控
• 指派 DRI：为每个工作流命名单一直接负责人，避免责任稀释
• 逆向排期：从检查点日期倒推出 12 个周里程碑，而非拍脑袋填日期
• 设置节奏：配置周检查、双周同步及 30/60/90 天关键节点，保持信息透明
• 风险登记：参考原决策阶段四（devil's-advocate）的反面意见，提前建立风险清单
• 输出与通知：计划保存至 ~/.claude/execution/YYYY-MM-DD-.md，并自动通知所有 DRI

适用边界与注意点

• 前提：输入必须是已批准、明确的决策，而非模糊方向；若仍需讨论，请先使用 /cs:decide
• 时间范围：90 天是刻意选择——长到能出现真实信号（而非忙碌），短到可及时纠偏；不适合超过一个季度的目标
• 动态调整：若某检查点揭示原决策需要重审，技能将路由到 /cs:boardroom 而非强制执行
• 收尾：90 天结束或触发终止条件时，应流转至 /cs:post-mortem 进行复盘
• 配套依赖：建议与 coo-advisor、strategic-alignment、change-management 技能协同使用

该技能本质上是决策到执行的转换器：不替你做决策，不替你管日常，但在决定与行动之间架起一座可追踪的桥。

What Problem It Solves

Most decisions die between "we decided" and "what's next Monday?" Teams produce an approved record but lack a structured way to turn commitments into concrete actions, leaving owners unclear, milestones undefined, and checkpoints unowned. This skill bridges that gap by expanding a decision document into an executable 90-day roadmap with explicit ownership, timelines, and review rhythms.

Core Capabilities & Workflow

Given an approved decision record (e.g., the output of /cs:decide), the skill performs:

• Workstream decomposition: Breaks the chosen option into 3–6 parallel streams to keep scope manageable
• DRI assignment: Names a single directly responsible individual per stream, avoiding dilution
• Reverse scheduling: Derives 12 weekly milestones from the final checkpoint date—no arbitrary dates
• Cadence setup: Configures weekly check-ins, bi-weekly syncs, and 30/60/90-day gates for transparency
• Risk register: Cross-references the devil's-advocate concerns from Phase 4 to pre-build a risk log
• Output & notification: Saves the plan to ~/.claude/execution/YYYY-MM-DD-.md and notifies all DRIs

Scope & Caveats

• Input requirement: Must receive a finalized, approved decision; if the direction is still fuzzy, use /cs:decide first
• Time horizon: 90 days is intentional—long enough for real signal (not just activity), short enough to course-correct; not suitable for goals spanning multiple quarters
• Dynamic re-routing: If a checkpoint reveals the original decision needs revisiting, the skill routes to /cs:boardroom rather than forcing execution
• Closure: At day 90 or upon kill criteria, transition to /cs:post-mortem for retrospective analysis
• Companion skills: Works best alongside coo-advisor, strategic-alignment, and change-management

The skill acts as a decision-to-execution converter: it doesn't make decisions for you or manage daily operations, but it builds a traceable bridge between intent and action.