← ClaudeAtlas

next-tasklisted

Works through an MVP plan made by mvp-to-tasks one task per session, loading only lean context (the project brief, the handoff notes of the tasks it depends on, and the task's listed files) so each session stays inside a usage-limited plan's window (tuned for Claude Pro's 5-hour limit; works in any agent that supports skills). Checks off sub-tasks as checkpoints, resumes interrupted tasks, writes a short handoff note for the next session, runs light tasks on a fast model and heavy tasks on the strongest one (automatically via subagents where available, e.g. Claude Code; otherwise recommends a model), and syncs status to Linear/Jira/Trello if linked. Use when the user says "next task", "continue the MVP", "work on T-012", "resume", or "what's next".
rckycls/mvp-to-tasks · ★ 0 · AI & Automation · score 67
Install: claude install-skill rckycls/mvp-to-tasks
# Next task: build one task with lean context This skill does one task per session. It loads as little as possible, writes a handoff, and then stops. That keeps each session small enough to fit in a usage window, and the handoff lets the next session pick up where this one ended without the previous conversation. ## Step 1: Find the plan - Look for `.mvp/tasks.md` and `.mvp/brief.md` at the project root. - If they're missing, check whether the user linked a PM tool project that has "T-xxx · " items. If so, work from the tool, using the item description as the task. - If there is no plan at all, say so and suggest running **mvp-to-tasks** first. Stop. ## Step 2: Pick the task Choose the task in this order: 1. If the user named a task ("work on T-012"), use that one. 2. Otherwise, **resume** any task marked `[~]`, starting at its first unchecked sub-task. 3. Otherwise, if a phase is fully `[x]` but has no passed exit check, run its **Phase exit check** (below) instead of a task. 4. Otherwise, take the first `[ ]` task whose dependencies are all `[x]`. State which task you picked and why in one line, e.g. "Resuming T-004 at sub-task 3/4." If every remaining task is blocked, list what blocks each one and stop. ### Resuming an interrupted task (`[~]`) The previous session may have been cut off by the usage limit with no warning, so don't assume it stopped cleanly. Before doing any new work: 1. **Read the checkpoint notes** in `.mvp/handoffs/T-xxx.wip.md`. They record every fi