Agent skill · Documentation

whiteboard-to-spec

Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Use when given whiteboard photos after a workshop, sketch images of a flow or architecture, or asked to 'write up what we drew'. Produces a structured write-up — decisions, flows, open questions, owners — that preserves everything on the board and flags what was ambiguous. Requires image input.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill whiteboard-to-spec --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/whiteboard-to-spec/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Whiteboard To Spec Skill The whiteboard is where teams decide; the photo of it is where decisions go to die. This skill reads the photo like the person who was in the room — arrows, crossings-out, shorthand, spatial grouping — and produces the write-up that should have been made that afternoon. ## What This Skill Produces - A **faithful transcription** of everything legible on the board, organised by its spatial grouping - The **structured spec**: decisions made, flows/diagrams redrawn as text or Mermaid, options considered (including crossed-out ones — rejections are decisions), open questions - An **ambiguity ledger**: what couldn't be read or could mean two things, flagged instead of guessed ## Required Inputs - **The image(s)** — one or more photos of the board/wall/sketch. If none is attached, ask for it; never proceed on a verbal description alone. - **Context** (ask if missing): what was the session about, who attended, what decision it served ## Reading Method 1. **Transcribe first, interpret second.** Pass one lists what is physically on the board, region by region (top-left, centre…), including arrows, boxes, colours, underlines, and crossings-out. Do not skip marginali

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Reading Method
  4. Output Format
  5. Board write-up: [session topic] — [date]
  6. Quality Checks
  7. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the whiteboard-to-spec skill do?

Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Use when given whiteboard photos after a workshop, sketch images of a flow or architecture, or asked to 'write up what we drew'. Produces a structured write-up — decisions, flows, open questions, owners — that preserves everything on the board and flags what was ambiguous. Requires image input.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill whiteboard-to-spec --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going