whiteboard

Name: whiteboard
Availability: InStock
Author: theycallmeholla

Manages project planning via a persistent GitHub Issues whiteboard.

Updated Jul 23, 2026

Search Tags:#workflow #planning #project management #collaboration #github #decision tracking

Ready to run

npx skills add https://github.com/Theycallmeholla/skills --skill whiteboard-theycallmeholla

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: whiteboard
Source: https://github.com/Theycallmeholla/skills/tree/main/skills/whiteboard
Command: npx skills add https://github.com/Theycallmeholla/skills --skill whiteboard-theycallmeholla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the issue of losing context and momentum in large, multi-session projects by maintaining a persistent, shared planning artifact on GitHub Issues.

Core Features & Use Cases

Persistent Planning: Uses GitHub Issues as a shared whiteboard to track decisions, unknowns, and tasks across multiple sessions.
Structured Workflow: Enforces a clear lifecycle of Draw, Work, and Snapshot modes to ensure projects move from loose ideas to concrete deliverables.
Use Case: When a project is too large for a single session, use this skill to break it down into manageable, one-session tickets that track decisions rather than just code.

Quick Start

Invoke the whiteboard skill to begin planning your project by drawing a new map on GitHub.

Frequently Asked Questions about whiteboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage multi-session project planning without losing context?▼

Multi-session project planning requires a persistent shared artifact to track decisions and tasks across sessions. Using GitHub Issues as a whiteboard maintains a clear audit trail, decomposing large objectives into actionable, single-session tickets.

How do I break down a large project into single-session tasks?▼

Breaking down a large project involves decomposing broad objectives into manageable, single-session decision tickets. A structured workflow with Draw, Work, and Snapshot modes enforces a lifecycle moving loose ideas to concrete deliverables.

Do I need the GitHub CLI to track project decisions on GitHub Issues?▼

Yes, the GitHub CLI is required to automate issue creation, dependency tracking, and state management. This automation coordinates the persistent whiteboard and maintains the project lifecycle across multiple sessions.

What is the best way to track complex project decisions instead of just code changes?▼

Tracking complex project decisions is best handled by managing a persistent GitHub Issue-based whiteboard. This approach tracks decisions and unknowns rather than just code, maintaining momentum and context for large projects.

Can I use GitHub Issues for workflow planning across multiple sessions?▼

Yes, GitHub Issues can be used as a shared whiteboard for workflow planning across multiple sessions. This approach facilitates dependency tracking and state management, ensuring projects move from loose ideas to concrete deliverables.

What are the limitations of using a GitHub Issue whiteboard for project management?▼

A GitHub Issue whiteboard is limited to managing decision tracking and task decomposition. It enforces a specific lifecycle of Draw, Work, and Snapshot modes, which may not suit projects requiring real-time collaboration outside of GitHub.