What it proves
A deck utility can be more reusable when it flags the few outline problems that reliably make slides feel weak instead of trying to be a full presentation coach.
Planning artifacts
tiny-deck-linter turns last-minute deck softness into a visible repair list before review starts.
This guide exists because decks often fail in predictable ways: vague titles, crowded bullets, and outlines that hide the actual point of the slide. The repo keeps the scope narrow and the fix list short.
Why this repo carries the track
A short site-side guide before the proof layer on GitHub.
Why it matters in this track
It fits the planning-artifact track because the output is a concise repair list for the deck, which is exactly the artifact the next edit pass needs.
What survives the first run
The linter findings are the artifact. They give the editor a short punch list for tightening titles and bullets before the deck goes wider.
What the first useful success looks like
tiny-deck-linter as a first useful success, not only a demo.
The first useful run is not a presentation score. It is a short list of the titles and bullets most likely to make the deck feel soft, crowded, or vague during review.
Use this before executive reviews, before exporting a slide outline into PowerPoint, or anywhere a deck should get tighter without starting another round of subjective formatting debate.
python3 deck_linter.py sample_outline.md- weak title: 'Overview'
- too many bullets under 'Overview': 5
- bullet 1 under 'Overview' is too long
- bullet 2 under 'Overview' is too long
- title too long: 'What Changed In The Last Two Quarters Across The Entire Business'Where it routes next
Calls out the outline problems that make decks feel soft, crowded, or vague before review.