← ClaudeAtlas

goal-action-planlisted

Structure operational plans, incident response playbooks, outage management, and complex project execution using a standardized 5-section Goal Action Plan framework. Use whenever the user asks for an action plan, incident response structure, launch plan, or multi-team execution playbook.
usct01/high-reliability-docs · ★ 1 · AI & Automation · score 72
Install: claude install-skill usct01/high-reliability-docs
# 5-Section Goal Action Plan Skill Organize complex operations, incident responses, and multi-team projects into a fixed 5-section execution framework so every stakeholder knows the objective, their exact task, and the escalation path. ## 1. Core Principles - **Leadership Intent & End State:** Clearly define what success looks like when the operation is complete. - **Single-Sentence Objective:** Section 2 must contain a single sentence answering **Who, What, When, Where, and Why (In order to...)**. - **Task and Purpose:** Every assigned team or owner must receive both a **Task** (what to do) and a **Purpose** (why they are doing it) so they can adapt if conditions change. - **Time Format:** Use 24-hour time with an explicit time zone (e.g., `08:00 UTC` or `13:30 IST`). ## 2. Mandatory 5-Section Structure Format every plan using these exact five top-level sections: ```text # GOAL ACTION PLAN: [INITIATIVE / INCIDENT NAME] **Timestamp:** [DD Month YYYY, HH:MM TZ] **Primary Time Zone:** [e.g., UTC / IST / EST] ## 1. CONTEXT & IMPACT - **Current Situation / Root Cause:** [What is happening right now? Include root cause, customer/system impact, and constraints.] - **Available Teams & Dependencies:** [Participating teams, external vendors, or upstream services.] - **Assumptions:** [Key assumptions required for this plan to succeed.] ## 2. OBJECTIVE [WHO] will [WHAT - core action] no later than [WHEN] at [WHERE] in order to [WHY - overarching goal]. ## 3. EXECUTION - **Leader