โ† ClaudeAtlas

ship-nextlisted

{{ ๐›€๐›€๐›€ }} Autonomously run the full delivery loop for the next roadmap task โ€” suggest, worktree, implement, roadmap-sync, PR, self-review
JasonWarrenUK/goblin-mode ยท โ˜… 5 ยท Web & Frontend ยท score 73
Install: claude install-skill JasonWarrenUK/goblin-mode
# Ship: Next โ€” the full delivery loop, unattended Orchestrates four existing skills (`task-suggest`, `roadmap-maintain`, `pr-create`, `pr-review-comment`) plus the mechanical git/test/lint work between them into one autonomous cycle: pick a task, build it in isolation, keep the roadmap coherent, open a PR, self-review it, fix what's actionable. This skill does not reimplement any of those four skills' methodology โ€” it invokes them and carries their outputs forward. Where this file's instructions and a called skill's own instructions conflict on *how* to do that skill's job, the called skill wins; this file only owns sequencing, the git/test/lint mechanics between them, and the hard rules below. ## Hard rules (never break these) 1. **Roadmap files are never hand-edited.** `.claude/roadmaps.json` is the only source of truth. Never directly edit the PHASE file's task list, the Mermaid block, `ROADMAP_OVERVIEW.md`, or the HTML artefact โ€” those are `roadmap-maintain`'s job, driven off `roadmaps.json`. If something about the roadmap looks wrong, fix `roadmaps.json` (or flag it) and let `roadmap-maintain` propagate it. 2. **Never run `git stash` blind.** Before any stash, run `git status` and `git stash list` first, and only stash what those show is genuinely in the way. Prefer not stashing at all when a worktree already isolates the work. 3. **Unmet dependencies โ†’ stop and write `BLOCKED.md`, never guess.** If the suggested task turns out to have an unmet dependency, an ambiguo