tjboudreaux/cc-visualization-skills · Archived

tools-visual-retro

Facilitate retrospectives and experiment readouts using ASCII grids, timelines, and heatmaps for rapid comprehension.

First seen Mar 8, 2026

Installation

$ npx skills add tjboudreaux/cc-visualization-skills --skill tools-visual-retro

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tjboudreaux/cc-visualization-skills.

npx skills add tjboudreaux/cc-visualization-skills

Browse all from tjboudreaux/cc-visualization-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,469 B
  • docs SUMMARY.md 143 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 15 installs

SKILL.md

Visual Retro Templates

Intent

  • Make retrospective insights digestible for visual learners without slideware.
  • Standardize text-based templates for PRs, issues, or shared docs.

Inputs

  1. Retro categories (Went Well, Risks, Next Bets, Metrics).
  2. Key quantitative results and qualitative highlights.
  3. Owners + follow-up items.

Workflow

  1. Pick template

- Grid: `` +------------+------------------+ | Went Well | Needs Attention | +------------+------------------+ | ... | ... | ` - Timeline w/ milestones. - Heatmap: use [] intensity markers ([++], [+], [~], [!]`).

  1. Populate data

- Keep bullet lines short; include metric deltas (+12% DAU). - Tag owners (@name) next to action items.

  1. Embed artifacts

- Link to logs, dashboards, or experiment IDs inline.

  1. Distribute

- Paste into PR descriptions, GitHub Discussions, or Slack posts. - Optionally store canonical version under .factory/retros/<date>.txt.

  1. Iterate

- Add “Next Checkpoint” section to set evaluation date.

Verification

  • Template fits within 80 characters width; column headers aligned.
  • Each action item shows owner + due date.
  • Retro artifact linked in change summary or issue comment.