codingthefuturewithai/plugins/teamcraft/skills/work-board

Goal

Make the dashboard usable immediately on invocation. Two things happen, every single time:

1. Refresh the dashboard at a stable user-side path. Copy ${CLAUDE_PLUGIN_ROOT}/skills/work-board/dashboard.html to ~/.claude/teamcraft-board.html, overwriting unconditionally. The stable path is what keeps the user's browser-side state (IndexedDB project handles) persistent across plugin upgrades — the plugin-cache path includes the version segment, which would otherwise blow away saved projects on every update.

2. Launch the dashboard, and always print the URL. Auto-launch the file in the user's default browser using whatever mechanism is available in the current environment. Always print the file:// URL too — that's the universal fallback and the link the user bookmarks once for one-click future access.

The dashboard handles everything else: a Board / Status view toggle in the header (Status is a live analytics view — work by status, throughput, cycle time, aging alerts, blocked chains, recomputed on every poll, with no tokens and no regeneration step), a dropdown for adding/switching/removing projects, polling each project's .teamcraft/work/ for changes, drag-and-drop with copy-as-prompt round-trip, and click-card-for-detail with relationship visualization. The Status tab is the live counterpart to the in-session /project-status text read.

What to Do

1. Copy the dashboard to a stable location. Source: ${CLAUDE_PLUGIN_ROOT}/skills/work-board/dashboard.html. Destination: ~/.claude/teamcraft-board.html. Always overwrite. If ~/.claude/ doesn't exist, create it.

2. Launch the dashboard. Don't ask permission — running this skill is the request to launch. Use whatever mechanism actually works in the current environment:

• macOS: open ~/.claude/teamcraft-board.html
• Linux: xdg-open ~/.claude/teamcraft-board.html
• Windows: start "" "%USERPROFILE%\.claude\teamcraft-board.html"
• Claude Cowork / headless / any environment where shell-based browser launching isn't available: skip the launch attempt silently and rely on step 3

If the launch command exits non-zero, don't error — just note "couldn't auto-launch in this environment" and continue.

3. Always print the file:// URL. Form it as file://<absolute-path> and print it as the final line. Most terminals render it clickable. This is the universal fallback when auto-launch isn't possible, and the durable link the user can bookmark once for direct future access — no Claude needed.

4. On the user's first run only, briefly tell them what to do: click the project name in the header → "Add a project…" → pick the project's .teamcraft/ folder → grant read access. The browser remembers each added project; subsequent runs of this skill just re-launch the same dashboard. The user can add as many projects as they want and toggle between them from the dropdown.

Constraints

• Always copy. Plugin upgrades must flow through; never skip the copy on the assumption that the file exists.
• Always try to launch. Auto-launch is the default — never gate it behind a confirmation question.
• Always print the URL. Even if auto-launch succeeded. The URL is the bookmarkable handle.
• Write only ~/.claude/teamcraft-board.html. That's the single managed artifact this skill produces. No regeneration step, no per-project state files, no other side effects on the filesystem. Project state lives in the browser's IndexedDB.
• Don't run scripts to build the dashboard. The bundled HTML is the dashboard. Plugin updates replace it; this skill just copies and launches.