aiwfx-whiteboard

Synthesizes open planning-tree items into a tiered landscape, recommended sequence, and decision fork.

Updated May 9, 2026
One-click install
npx skills add https://github.com/23min/aiwf --skill aiwfx-whiteboard-23min
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aiwfx-whiteboard
Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded-rituals/plugins/aiwf-extensions/skills/aiwfx-whiteboard
Command: npx skills add https://github.com/23min/aiwf --skill aiwfx-whiteboard-23min

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project's planning state lives in many markdown entities (epics, milestones, ADRs, gaps), it is hard to answer "what should I work on next?" without re-reading everything. This Skill reads the aiwf planning tree and turns scattered open work into a prioritized, actionable synthesis. ## Core Features & Use Cases - Tiered open-work landscape: Classifies every open epic, milestone, gap, and ADR into five tiers by leverage on future work, from compounding fixes to defer-until-forced items. - Recommended sequence and first-decision fork: Produces a numbered before/after/parallel action sequence plus an A/B/C option fork with pros, cons, and an explicit lean. - Pending-decision Q&A gate: Walks open decisions one at a time with context, options, and a lean, never batching questions. - Gitignored WHITEBOARD.md cache: Writes a regeneratable snapshot of the synthesis that is never committed, keeping the live tree as the single source of truth. - Use Case: After several sessions of planning, ask "what should I work on next?" and receive a tiered table of all open items, a concrete next-action sequence, and a guided walk through pending decisions. ## Quick Start Ask the assistant to draw the whiteboard and synthesize the open work in the current aiwf planning tree.

Frequently Asked Questions about aiwfx-whiteboard

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

FAQPage Schema
How do I decide what to work on next in an aiwf planning tree?▼

Invoke the whiteboard synthesis, which reads open epics, milestones, gaps, and ADRs via aiwf status, list, show, and history. It returns a recommended sequence with before/after/parallel framing, a first-decision fork with pros and cons, and a tiered landscape table.

How are open work items prioritized into tiers?▼

Items are classified by leverage on future work, not chronology. Tier 1 covers compounding fixes, Tier 2 foundational proposed ADRs, Tier 3 workflow rituals, Tier 4 cheap operational debris, and Tier 5 items deferred until a forcing function appears.

Does the whiteboard synthesis modify the planning tree or git history?▼

No, the synthesis is read-only over the planning tree with no mutation and no commit. It only writes a gitignored WHITEBOARD.md cache in the repo root, which is regenerated each run and never treated as a source of truth.

Can I keep my own TODO ordering alongside the generated synthesis?▼

Yes, a consumer-maintained ordering such as TODO.md is treated as the baseline and never rewritten. The skill renders a delta against it, dropping terminal items, proposing placements for new entities, and only suggesting moves where something changed.

What are the limitations of the whiteboard direction synthesis?▼

It only answers direction questions about open work and pending decisions. Refactor advice, design review, and cross-team coordination are out of scope, and it never invents aiwf verbs that do not exist, recording missing ones as follow-up gaps instead.