github-visual-planning-issues

name	github-visual-planning-issues
description	Create review-friendly GitHub planning issues that supersede stale/seasonal issues and include source-backed image thumbnails for faster human review.
version	1.0.0
author	Hermes Agent
license	MIT
triggers	["When a user asks to create a GitHub issue for a trip, plan, portfolio item, or other review artifact where pictures/examples make review easier","When an existing issue is stale/seasonal and the user wants a replacement issue rather than editing the old one in-place","When a GitHub issue body needs embedded images, candidate options, visual comparison tables, or stay/product/location previews"]
related_skills	["github-issues","github-comment-body-file-safety"]
tags	["github","issues","planning","visuals","markdown","shell-safety"]

GitHub Visual Planning Issues

Class of task

Use this for review-friendly GitHub planning issues where the deliverable is a structured issue body with visual thumbnails and links, especially when replacing or superseding a stale issue.

Workflow

1. Inspect the prior issue first

   • Use gh issue view <number> --repo <owner/repo> --json number,title,state,url,body,labels,comments.
   • Identify what is stale, seasonal, duplicated, or still useful.
   • If the issue is travel/season/date-sensitive, explicitly separate current-realistic expectations from seasonal/historical expectations (e.g., tulips, fall color, clear beach water, waterfall flow).

2. Search for duplicates / related issues

   • Use gh issue list --repo <owner/repo> --state all --search "key terms" --json number,title,state,url.
   • Reuse the old issue if it substantially covers the new request; otherwise create a replacement and cross-link.

3. Collect source-backed visuals and official links

   • Prefer official destination/vendor pages, repository assets, or credible pages that expose direct image URLs.
   • For travel/destination planning, capture both: (a) the official destination planning link, and (b) a direct preview image URL suitable for GitHub markdown.
   • Browser flow: navigate to source page → browser_get_images → choose images with meaningful alt, width/height, and stable URLs.
   • If direct images are hard to retrieve, inspect OpenGraph/Twitter metadata (og:image, og:title, description) with a small script and cite the source URL.
   • Do not download/rehost images unless explicitly needed; direct source URLs are enough for GitHub markdown review boards.

4. Draft a visual review board

   • Use compact tables with HTML thumbnails for predictable sizing:

| Option | Preview | Notes |
|---|---|---|
| Candidate A | <img src="https://example.com/a.jpg" width="260" alt="Candidate A exterior"> | Why this option matters |