How this command is triggered — by the user, by Claude, or both
Slash command
/dincoder:nextThe summary Claude sees in its command listing — used to decide when to auto-load this command
Display the highest-priority, unblocked tasks that are ready to work on now.
## Workflow
1. **Filter for Next Tasks**:
- Run `tasks_filter` with:
- `preset: "next"`
- `limit: 5`
- `sortBy: "priority"`
2. **Display Each Task**:
- **Task ID**: [e.g., T042]
- **Description**: [one-liner]
- **Metadata**:
- Phase: [phase]
- Type: [type]
- Priority: [high/medium/low]
- Effort: [hours]
- **Why Ready**: No blocking dependencies
3. **Recommend Starting Point**:
- Analyze priorities
- Consider current phase
- Suggest which task to start f...Display the highest-priority, unblocked tasks that are ready to work on now.
Filter for Next Tasks:
tasks_filter with:
preset: "next"limit: 5sortBy: "priority"Display Each Task:
Recommend Starting Point:
Offer Details:
npx claudepluginhub flight505/dincoder-plugin --plugin dincoder/pickupShows ready tasks sorted by priority, helps select one, and starts it with full context including related learnings and decisions. Accepts optional task ID.
/list-tasksLists tasks with intelligent argument parsing, supporting filters by status, priority, IDs, and special views like subtrees and blocked tasks.
/pm-nextShows next N (default 3, max 10) highest-priority unblocked PENDING tasks for a project, with scores, research status, HITL flags, and suggestions to run /pm:work.
/nextShows the next pending task with context and related knowledge, then starts working on it on user confirmation.
/figure-out-what-to-work-onGuides selection of the next work item from a priority-sorted backlog, checking for blockers and dependencies. Supports creating questions for blocked items.
/nextSuggests the next prioritized action based on current project state, task hierarchy, and quality gates.