Update to Management Consulting

{
  "description": "Create and refine consulting reports, decision memos, and executive presentations, including storylines, exhibits, visual design, and artifact review. Use for board readouts, investment committee memos, steering updates, and final reports. For sales proposals and pitch decks, use proposal-development when available.",
  "included_files": [
    {
      "relative_path": "references/executive-presentations.md",
      "size_in_bytes": 4360
    },
    {
      "relative_path": "references/pptx-generation.md",
      "size_in_bytes": 6637
    },
    {
      "relative_path": "references/slide-design.md",
      "size_in_bytes": 7137
    },
    {
      "relative_path": "references/written-reports.md",
      "size_in_bytes": 3533
    },
    {
      "relative_path": "scripts/consulting-charts.cjs",
      "size_in_bytes": 4711
    }
  ],
  "name": "client-deliverables",
  "skill_md_contents": "---\nname: client-deliverables\ndescription: \"Create and refine consulting reports, decision memos, and executive presentations, including storylines, exhibits, visual design, and artifact review. Use for board readouts, investment committee memos, steering updates, and final reports. For sales proposals and pitch decks, use proposal-development when available.\"\nlicense: MIT\nmetadata:\n  category: communication\n  version: \"2.2.0\"\n  author: Anot\n---\n\n# Client Deliverables\n\nTurn the analysis into an artifact that enables the intended decision and survives scrutiny. Establish the audience, decision, evidence base, requested format, and reading or presentation conditions from the user's context. Preserve supplied templates, branding, section order, accessibility needs, and length constraints.\n\nUse available evidence and complete the portions it supports. Mark missing proof points or pending decisions where they matter; ask only when a missing answer blocks a useful result. Do not invent a number, source, owner, date, testimonial, or case result to fill a design. Distinguish proposed actions from agreed commitments.\n\n## Build the argument\n\nLead with the answer, decision request, or the uncertainty that prevents a decision. Organize supporting arguments by what the audience needs to assess the recommendation. Situation-complication-question-answer can help develop the story; it does not require delaying the answer or showing those labels.\n\nUse takeaway titles for analytical sections and slides when they aid comprehension. Keep navigational labels or prescribed headings where the template requires them. The headline must be supported by the exhibit and its qualifications. Do not turn an association into a causal claim or a forecast into an achieved result.\n\nConnect each consequential claim to its source or calculation. Keep units, periods, definitions, and scenario names consistent throughout. Show contradictions and decision-changing limitations near the claim they qualify. Separate observed results, forecasts, judgment, and illustrative examples. A conditional sentence still needs a basis if it asserts an empirical pattern.\n\nConcentrate detail on the trade-offs, financial and operational implications, and actions that determine this decision. Use compact tables for comparisons and prose for reasoning. There is no required sentence count, supporting-argument count, or deck length.\n\n## Choose the artifact\n\nFollow an explicit format request. If the format is open, a memo or report suits asynchronous scrutiny; a presentation suits a discussion with visual evidence. A read-ahead deck needs more self-contained explanation than a projected presentation. Produce multiple formats only when requested or needed for the stated use.\n\n- For reports, decision briefs, and investment committee memos, read [written reports](references/written-reports.md).\n- For executive decks, exhibit selection, discussion design, and backup, read [executive presentations](references/executive-presentations.md).\n- When designing or substantially revising slides, read [slide design](references/slide-design.md) for visual direction, composition, analytical emphasis, and review across the deck.\n- When producing a PowerPoint file with code, read [PPTX generation](references/pptx-generation.md). The optional bridge helper is a tool-specific implementation, not a requirement for other presentation tools.\n\nUse the host's available document, spreadsheet, or presentation tools and relevant format skills if available. This skill supplies consulting content and review criteria; it does not depend on a particular agent or installed plugin. For a requested file, create the file when tools permit. If creation or rendering is unavailable, state the limitation and deliver the usable portion without claiming a finished artifact.\n\n## Check before delivery\n\nCheck that the executive summary stands alone, the recommendation follows from the evidence, and the requested decision is explicit. Reconcile figures across prose, tables, charts, and appendices. Test that a chart actually represents the intended relationship, not merely that it renders.\n\nFor files, open or parse the saved artifact, refresh calculations where supported, and inspect rendered pages or slides. Check clipping, overlap, legibility, pagination, source notes, and navigation at the intended reading size. Inspect material revisions again, stopping once the affected checks pass. Give the user the artifact and a concise account of material assumptions or verification limits.\n\nFor decks, also inspect the slides together. A sequence of correctly aligned but repetitive text boxes can still be a weak presentation. Use layout, scale, and visual emphasis to make the argument easier to understand while retaining the client's visual identity. Keep drafting and validation commentary out of the delivered content.\n"
}