next
Analyze and pick the next task to work on. Reads MASTER_PLAN.md, scores tasks by priority and status, and presents interactive selection. Use when starting a…
Task completion workflow — run tests, commit, push, and update MASTER_PLAN.md. Use when a task is finished and ready to ship. Triggers on "/done", "mark done", "task complete", "finish task", "ship it".
$ npx -y skills add endlessblink/master-plan --skill done --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/doneContext preview
The summary Claude sees to decide when to auto-load this skill.
Task completion workflow — run tests, commit, push, and update MASTER_PLAN.md. Use when a task is finished and ready to ship. Triggers on "/done", "mark done", "task complete", "finish task", "ship it".
name: done description: Task completion workflow — run tests, commit, push, and update MASTER_PLAN.md. Use when a task is finished and ready to ship. Triggers on "/done", "mark done", "task complete", "finish task", "ship it".
Finalize a completed task: verify tests pass, commit changes, update MASTER_PLAN.md, and push.
Run git status to see what files were modified:
git status git diff --stat
Output immediately:
Files changed: - [list of modified files]
Use `AskUserQuestion` to collect:
1. **Task ID** (header: "Task ID")
2. **Run tests?** (header: "Tests")
Then ask in plain text: "What's a brief summary of the changes? (1-2 sentences)"
**IMPORTANT**: Wait for user to provide the summary before proceeding.
Detect and run the project's test command. Check in order: 1. If `package.json` exists → `npm test` 2. If `Cargo.toml` exists → `cargo test` 3. If `pyproject.toml` or `setup.py` exists → `pytest` 4. If `Makefile` with `test` target → `make test` 5. If `go.mod` exists → `go test ./...`
**If tests fail**: STOP immediately. Report failures. Do NOT proceed. **If tests pass**: Continue. **If no test command found**: Warn user and continue.
**Skip this step if user selected "Quick fix (no task ID)".**
**CRITICAL**: Tasks may appear in **multiple locations**. Update ALL of them:
Find the task row and update:
# Before: | **TASK-XXX** | **Title** | **P2** | PLANNED | ... | # After: | ~~**TASK-XXX**~~ | ✅ **Title** | **P2** | ✅ DONE (YYYY-MM-DD) | ... |
# Before: - TASK-XXX: Description # After: - ~~TASK-XXX~~: ✅ Description
# Before: ### TASK-XXX: Title (IN PROGRESS) # After: ### ~~TASK-XXX~~: Title (✅ DONE)
Search for the task ID and confirm all occurrences show strikethrough or ✅ DONE:
grep "TASK-XXX" docs/MASTER_PLAN.md
Stage all relevant files. **NEVER commit**:
Prefer staging specific files by name over `git add -A`.
# Stage code files git add <changed-files> git add docs/MASTER_PLAN.md # if tracked task # Commit git commit -m "$(cat <<'EOF' feat(TASK-XXX): Brief summary from user - Key change 1 - Key change 2 Co-Authored-By: Claude <noreply@anthropic.com> EOF )" # Push git push
**For quick fixes (no task ID):**
git commit -m "$(cat <<'EOF' fix: Brief summary from user Co-Authored-By: Claude <noreply@anthropic.com> EOF )" git push
**Commit prefix conventions:**
Output this summary:
## Task Complete - **Task**: TASK-XXX (or "Quick fix") - **Summary**: [user's summary] - **Tests**: ✅ Passed (or ⏭️ Skipped) - **Commit**: [short hash] — [message] - **Push**: ✅ Pushed to origin - **MASTER_PLAN.md**: Updated / N/A
1. **NEVER skip commit/push** — Changes must be pushed to the remote 2. **ALWAYS collect summary** — Don't proceed without knowing what changed 3. **Update ALL locations** in MASTER_PLAN.md for tracked tasks 4. **Verify with grep** after updating MASTER_PLAN.md 5. **Wait for user input** — Don't assume or skip questions 6. **Test failures block completion** — If tests fail, stop and report
AI-native task management for Claude Code. Track tasks in a MASTER_PLAN.md file, pick what to work on, save progress, and ship — all through agent skills.
Analyze and pick the next task to work on. Reads MASTER_PLAN.md, scores tasks by priority and status, and presents interactive selection. Use when starting a…
Save work-in-progress and push to remote. Like /done but keeps task IN PROGRESS. Use when switching machines, ending a session, or backing up work. Triggers on…
Create a new task in MASTER_PLAN.md with auto-generated sequential IDs. Supports TASK, BUG, FEATURE, and INQUIRY types. Triggers on "/task", "add task", "new…