Skip to main content

MARP Presentation Generator

Generate MARP-format presentation slides from existing ArcKit project artifacts, suitable for governance boards, stakeholder briefings, and gate reviews.

Command

arckit presentation <project ID and audience>

Arguments

  • project (required): Project identifier (ID or name)
  • audience (optional): Target audience (executive/technical/stakeholder/procurement)

Examples

arckit presentation "001 executive board"
arckit presentation "NHS appointment booking technical"

Purpose

Create an ARC-{PROJECT_ID}-PRES-v{VERSION}.md document that serves as:
  • A slide deck in MARP format (renders to PDF/PPTX/HTML)
  • A governance-ready summary drawing from existing ArcKit artifacts
  • A tailored presentation for different audiences

Interactive Configuration

The command asks two questions before generating:

Question 1: Focus (Audience)

  • Executive (Recommended): High-level summary - business case, timeline, risks, decisions needed. Fewer slides, minimal technical detail.
  • Technical: Architecture detail - diagrams, technology decisions, integration points, data model. More slides, Mermaid diagrams.
  • Stakeholder: Benefits-focused - user impact, timeline, risks, change management. Balanced detail, emphasis on outcomes.
  • Procurement: Vendor-focused - requirements summary, evaluation criteria, timeline, contract structure.

Question 2: Slide Count

  • 10-12 slides (Recommended): Standard governance board deck
  • 6-8 slides: Brief update - executive summary, key decisions, next steps only
  • 15-20 slides: Comprehensive briefing - detailed sections with supporting data

Slide Deck Structure

6-8 Slide Deck

  1. Title
  2. Context & Objectives
  3. Architecture Overview
  4. Key Requirements
  5. Risk Summary
  6. Timeline
  7. Next Steps

10-12 Slide Deck

  1. Title
  2. Context & Objectives
  3. Stakeholder Landscape
  4. Architecture Overview
  5. Technology Decisions
  6. Key Requirements
  7. Risk Summary
  8. Roadmap & Timeline
  9. Compliance & Governance
  10. Recommendations & Next Steps
  11. Questions & Discussion

15-20 Slide Deck

  • All of the above + expanded sections
  • Data model
  • Integration points
  • Additional detail slides

Slide Content Sources

Title Slide: Project name, date, classification, presenter Context & Objectives (from STRAT, SOBC, REQ):
  • Business challenge and strategic opportunity
  • Key objectives and success criteria
Stakeholder Landscape (from STKE):
  • Key stakeholders with roles, interest, influence
  • Mermaid quadrant chart if data available
Architecture Overview (from DIAG, STRAT):
  • Current state summary and pain points
  • Target state and key changes
  • Mermaid C4 context diagram
Technology Decisions (from RSCH, AWSR, AZUR, GCRS, ADR):
  • Key build vs buy decisions
  • Technology choices with rationale
Key Requirements (from REQ):
  • Summary counts by category (BR/FR/NFR/INT/DR)
  • Top 3-5 critical requirements
Risk Summary (from RISK):
  • Top 3-5 risks with likelihood/impact/mitigation
  • Mermaid pie chart of risk distribution
Roadmap & Timeline (from PLAN, ROAD):
  • Mermaid Gantt chart of project phases
  • Key milestones with status
Compliance & Governance (from TCOP, SECD, MSBD, DPIA, AIPB):
  • Standards compliance status table
  • Only included for UK Government or compliance-heavy projects
Recommendations & Next Steps:
  • Immediate actions with owners and deadlines
  • Decisions required from the audience
Questions & Discussion: Contact details and next review date

MARP Formatting

  • Uses --- between slides (MARP slide separator)
  • Includes MARP YAML frontmatter: marp: true, theme: default, paginate: true
  • Uses header and footer for persistent slide branding
  • Keeps each slide to 3-5 bullet points or one table/diagram
  • Uses Mermaid diagrams where data supports them
  • Uses <!-- fit --> for headings that need auto-sizing
  • Tables: no more than 5 rows per slide

Mermaid Label Rules

CRITICAL - Applies to ALL Mermaid diagrams, especially quadrantChart:
  • No accented characters: Use ASCII only - replace é→e, í→i, ó→o, ñ→n, ü→u
  • No hyphens in data point labels: Use spaces instead
  • No special characters: Avoid colons, parentheses, brackets, quotes
These restrictions exist because Mermaid’s parser breaks on non-ASCII and certain punctuation.

Output

Generates ARC-{PROJECT_ID}-PRES-v{VERSION}.md with:
  • MARP YAML frontmatter
  • Title slide
  • Content slides based on focus and count selections
  • Mermaid diagrams (Gantt, pie, C4, quadrant)
  • Questions slide
CRITICAL: Use Write tool for file creation. Show ONLY concise summary to user.

Rendering the Presentation

The output .md file can be rendered using:

MARP CLI

# Install MARP CLI
npm install -g @marp-team/marp-cli

# Render to PDF
marp --pdf ARC-001-PRES-v1.0.md

# Render to PPTX
marp --pptx ARC-001-PRES-v1.0.md

# Render to HTML
marp ARC-001-PRES-v1.0.md

VS Code Extension

  1. Install MARP for VS Code
  2. Open the .md file
  3. Click “Open Preview” or use Ctrl+K V
  4. Export to PDF/PPTX/HTML from preview

Prerequisites

Minimum Artifact Check: A meaningful presentation requires at least 3 artifacts. If fewer, the command warns:
⚠️  Warning: This project only has [N] artifacts.

A useful presentation typically requires at least:
- Architecture principles (global)
- Stakeholder analysis or requirements
- Risk register or project plan

Run more /arckit commands first, then re-run /arckit:presentation.
MANDATORY (warn if missing):
  • PRIN (Architecture Principles) - Governance standards
RECOMMENDED (read if available):
  • STKE (Stakeholder Analysis) - Stakeholder slide
  • REQ (Requirements) - Requirements slide
  • RISK (Risk Register) - Risk slide
  • PLAN (Project Plan) - Timeline slide
  • ROAD (Roadmap) - Roadmap slide
  • STRAT (Architecture Strategy) - Context slide
  • SOBC (Business Case) - Executive summary
  • DIAG (Architecture Diagrams) - Architecture slide
  • WARD (Wardley Map) - Strategy slide
  • Research (RSCH, AWSR, AZUR, GCRS) - Technology decisions
  • Procurement (SOW, DOS) - Procurement status
  • Design reviews (HLDR, DLDR) - Quality assurance
  • Compliance (TCOP, SECD, MSBD) - Compliance slide
  • arckit story - Full narrative companion document
  • arckit pages - Generate documentation website

Resources

Build docs developers (and LLMs) love