← ClaudeAtlas

artifact-planlisted

Tracks a large task on a live plan board (an artifact showing the tasks, their order, and what blocks what) instead of a markdown plan file. Use when a request splits into 3 or more tasks with dependencies between them, when the orchestrate skill splits work across sessions, or when the user says "plan this", "track this", "make a plan board". Offers the board first and builds it only on a yes. Also use whenever this session orchestrates work tracked on a plan board: a child's report, approach note or question about a `Plan task:` id, deciding what to write to the board, and resuming after a restart.
ShiJianXi/molt · ★ 1 · Data & Documents · score 67
Install: claude install-skill ShiJianXi/molt
# Artifact plan One **plan board** per large task. The orchestrator (the session the user talks to) creates it, is the **only writer**, and updates it as implementation agents report. Agents never touch it. The page is written from `board-page.md` in this skill's directory; the data lives in the board's database, so updates are database writes, never republishes. ## 1. Detect Offer a plan board when all of these hold: - the work splits into **3 or more** tasks that can each be finished and checked on their own; - at least one task **depends on** another (needs its output, or touches the same files after it); - it will run across several sessions or agents, or take more than about an hour. Below that, just do the work. Never offer twice in one session after a "no". ## 2. Offer Ask with `AskUserQuestion`, one question: > This splits into N tasks, and K of them wait on others. Track it on a plan board? Options: **Track it on a plan board (Recommended)** and **Just start**. On "Just start", go on without one. If the Artifact tool or `ArtifactData` isn't available in this session, say so in one line and go on without one. ## 3. Build the task graph Write the tasks before publishing anything. Each task has: | field | meaning | |-------------|----------------------------------------------------------------------| | `id` | `T1`, `T2`, ... (the doc id), stable for the life of the plan | | `tit