Leadership Artifact Skill

---
name: leadership-artifact
description: Assemble genuine prepared leadership notes, individual drafts, decision records and reminder evidence into a polished navigable meeting page.
---

# Leadership artifact

Read the [shared contract](../meetings-and-follow-through/references/working-contract.md). Receive actual results from the caller: notes, one draft per recipient, decision records, personal reminder proposals, unresolved questions and any actual action receipts. Read [the page design](references/page-design.md) when producing a page.

Make the work easy to inspect and use. Open with the meeting's purpose and the small set of decisions or questions that need the leader's attention. Provide visible navigation to notes, follow-ups, decisions and reminders, using only sections that have content. Make each recipient's draft independently readable and easy to copy. Keep source references near consequential claims without crowding the reading path.

Separate prepared drafts, proposed reminders and verified saved actions in both labels and content. A draft can be complete while its message remains unsent. A personal reminder proposal can be ready to approve while no destination entry exists. Where a write has an uncertain outcome, show that state and the known evidence; do not promote the proposal to completed work.

Use the house style in the linked design reference, readable on desktop and mobile with light and dark themes. Do not add decorative dashboards, synthetic activity or an implied performance gain. Produce the page from genuine task results after the workflow has actually run in its target environment; this instruction pack alone is not an output example. If page tooling is absent, return coherent Markdown with the same content hierarchy and identify the format used.

Read the entire page, test navigation and copying where the environment permits, and inspect both themes at a narrow viewport. Trace each major agreement through notes, draft and any personal action evidence. Return the actual saved or displayed page location, source links and known format or verification limitations. If the leader corrects meaning, update affected sections together rather than leaving conflicting drafts on the page.

## Public reference files

[references/page-design.md](references/page-design.md) owns the portable house typography, palette and navigation guidance.

# Meeting page design

Use genuine meeting results supplied by the caller. Build a premium reading page with clear hierarchy and useful navigation; no sample HTML or pretend output accompanies this draft pack.

Use Newsreader serif for headings at weight 500; IBM Plex Sans for body text at 16px with line-height 1.62; IBM Plex Mono for small metadata, counters and data. Use a serif standfirst for the purpose. Prefer installed fonts or permitted font delivery, retaining serif/sans/monospace fallbacks when fonts cannot load. Font loading is not permission to send private meeting content to another service.

Light tokens: paper #F6F5F1, raised surface #FFFFFF, ink #1B1E20, secondary ink #4A4E52, muted #6E6A62, border #DEDBD3, rust accent #A8431E and soft rust #F7E7DF. Dark tokens: paper #15171A, raised surface #1D2024, ink #EBE8E2, secondary ink #B9B5AE, muted #8E8A83, border #2E3236, rust accent #E0784B and soft rust #3A241A. Paint an explicit body background. Honor system theme and provide a readable light/dark switch when page tooling permits. Rust is the meaningful accent; status must also be expressed in text.

Limit the reading width to about 1080px with comfortable side padding and generous section spacing. Headings balance naturally, with the main heading scaling between 40px and 68px. Use border-radius 3px for any separate surface. Keep surfaces quiet, with a fine border and subtle shadow only where content forms a distinct object. Tables scroll horizontally at narrow widths, with readable headers and aligned numeric data.

Put navigation links to the actual sections near the top. Give drafts one recipient per section or card, a subject where appropriate, complete copyable text and a visible draft label. For reminder proposals, show destination, title, purpose and exact timing together, followed by approval state. Verified action entries include their actual stable receipt and destination link/readback; do not decorate unresolved entries as successes. Decisions link to their actual record or carry an explicit draft label.

Use semantic headings, visible keyboard focus, accessible labels and sufficiently contrasting text. Keep all content readable without animation. Verify section links, copy behavior, theme switch and narrow-screen layout where those controls exist. Return the format and any inspection limitations with the page.