← ClaudeAtlas

executive-decision-memolisted

Draft, review, and format official executive memorandums, decision records, policy directives, and formal letters using strict Bottom Line Up Front (BLUF) and structured hierarchy rules. Use whenever the user asks to write an executive memo, decision record, policy directive, or formal business letter.
usct01/high-reliability-docs · ★ 1 · DevOps & Infrastructure · score 72
Install: claude install-skill usct01/high-reliability-docs
# Executive Decision Memo & Correspondence Standard Follow these standards whenever drafting or reviewing formal organizational correspondence, policy directives, and decision records. ## 1. Data Privacy & Security Guardrails - **Never process confidential, restricted, or Personally Identifiable Information (PII)** unless operating inside an authorized internal environment. - Replace real personal identifiers, account numbers, and sensitive internal endpoints with placeholders (e.g., `[FULL NAME]`, `[DEPT-CODE]`) when drafting in shared workspaces. ## 2. Core Writing Style - **Bottom Line Up Front (BLUF):** State the main decision, recommendation, or purpose in the very first paragraph. - **Active Voice:** Use active voice rather than passive voice (e.g., "The Engineering Director approved the budget," not "The budget was approved"). - **Conciseness:** Keep sentences short (aim for an average of 15 words or fewer) and paragraphs brief (under 5–6 lines). - **Plain Language:** Use simple, everyday words and avoid unnecessary jargon. Spell out acronyms on first use (e.g., `Standard Operating Procedure (SOP)`), except for universally known terms like `API` or `SLA`. ## 3. Formatting Rules - **Spacing:** Single-space within paragraphs; double-space between paragraphs. - **Dates:** Format dates unambiguously as `DD Month YYYY` (e.g., `11 November 2026`) for internal memorandums, or standard format (`November 11, 2026`) for external letters. - **Paragraph Numbering:** - `1.` (