# Flurdy Agent Skills Next > Next - Pick Your Next Bead - Skill: `tomevault-io/flurdy-agent-skills-next` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/flurdy-agent-skills-next` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/flurdy-agent-skills-next/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/flurdy-agent-skills-next --- # Next - Pick Your Next Bead Help select the next bead to work on based on readiness and user preferences. ## When to Use - Starting a new work session - Finished a task and need to pick the next one - Want to see what's available to work on - Need help prioritizing between multiple options ## Usage ```bash /next # Show ready beads, ranked by suitability /next safe # Same but exclude services with in-progress beads /next task # Auto-pick the next most suitable task and start it /next quick # Auto-pick an easy win (excludes busy services) /next bug # Auto-pick the next most important bug and fix it /next # Start working on specific bead ``` ## What This Skill Does 1. **Find Ready Work** - Run `bd list --ready` to get open, unblocked tasks - Excludes `in_progress` beads (another session may be working on them) - Show current in-progress work if any (for awareness, not selection) 2. **Rank by Suitability** - Apply priority ranking algorithm (see below) - Bugs generally rank higher than features at same priority - Epics rank lower (they represent larger work) 3. **Present Options** - Show top 5 candidates with key details - Include: ID, title, priority, type, labels (services/tags), age - Ask user to pick or provide different criteria 4. **Start Work** - Mark selected bead as in_progress - Show full bead details - Suggest first steps if description includes them ## Examples ```bash # Show ready work ranked by suitability /next # Show ready work, excluding services with in-progress beads /next safe # Auto-pick and start the next most suitable task /next task # Auto-pick an easy win (excludes busy services) /next quick # Auto-pick the next most important bug and start fixing /next bug # Start a specific bead /next mycode-abc ``` ## Output Format ```plaintext ## Ready to Work (5 of 12 open) | # | ID | Pri | Type | Labels | Title | |---|------------|-----|---------|---------------------|--------------------------------| | 1 | mycode-abc | P1 | bug | frontend | Fix login timeout issue | | 2 | mycode-def | P2 | feature | backend, orders | Add export to CSV | | 3 | mycode-ghi | P2 | task | auth | Update dependencies | | 4 | mycode-jkl | P3 | feature | frontend, css | Dark mode toggle | | 5 | mycode-mno | P3 | task | events, auth | Refactor auth service | Currently in progress: mycode-xyz "Implement caching layer" Which would you like to work on? (1-5, or specify ID, or "task" to auto-pick) ``` ## Implementation When invoked: 1. **Get the ranked table** using the `next-bd` script (handles ready list, blocked filtering, label fetching, and ranking in one command): ```bash # Preferred — if symlinked into the project's scripts/ ./scripts/next-bd --in-progress ``` Fallback if not available in the project's scripts/: ```bash SKILLS_DIR="${SKILLS_DIR:-${CODEX_HOME:-$HOME/.codex}/skills}" if [[ ! -x "$SKILLS_DIR/next/resources/next-bd" ]]; then SKILLS_DIR="${CLAUDE_HOME:-$HOME/.claude}/skills" fi "$SKILLS_DIR/next/resources/next-bd" --in-progress ``` For `safe` and `quick` modes, add `--avoid-busy` to exclude beads whose labels overlap with in-progress beads: ```bash ./scripts/next-bd --in-progress --avoid-busy ``` This outputs a markdown table ranked by the priority algorithm, with labels included, blocked beads filtered out, and in-progress beads shown for awareness. 2. Parse command argument: - (none): Show the script output, ask user to pick - `safe`: Show the script output with `--avoid-busy`, ask user to pick - `task`: Auto-select top-ranked bead and start it - `quick`: Auto-select an easy win task and start it (uses `--avoid-busy`) - `bug`: Auto-select top-ranked bug and start it (see Bug Mode below) - ``: Start that specific bead 3. If specific bead ID provided: ```bash bd show bd update --status=in_progress ``` 4. Otherwise, present the script output and ask user to choose 5. On selection: - Mark as in_progress - Show full details with `bd show` - If bead has description with steps, highlight first step ## Handling Edge Cases - **No ready beads (P0-P3)**: Show blocked beads and what's blocking them; mention P4 backlog exists if any, but don't auto-pick - **All open beads in progress**: Warn that another session may be working on them; ask user if they want to see in_progress beads anyway (may cause conflicts) - **User picks in_progress bead**: Warn that another session may be working on it; require explicit confirmation before starting - **Invalid ID**: Show error and list valid options - **User says "skip"**: Show next 5 options ## Priority Ranking Algorithm Rank ready beads in this order (first match wins): | Rank | Criteria | |------|---------------------------------| | 1 | Any P0 issue (any type) | | 2 | P1 bug | | 3 | P2 bug | | 4 | P1 feature or task | | 5 | P1 epic | | 6 | P2 feature or task | | 7 | P3 bug, feature, or task | | 8 | P2 epic | | 9 | P3 epic | | 10 | Any other non-P4 issue | **Important**: P4 items are backlog/future work and must NEVER be auto-picked. Always use `--priority-max=3` to exclude them. Only show P4 items if user explicitly requests them. ## Quick Task Heuristics When `/next quick` is used, prefer: 1. Type: task > bug > feature (tasks are usually smaller) 2. Priority: P3 > P2 > P1 (lower priority = less complex) 3. Exclude epics (too large for quick wins) 4. Title keywords: "fix", "update", "add" > "implement", "refactor", "redesign" ## Bug Mode When `/next bug` is used: 1. **Filter to open bugs only** (excluding P4 backlog): ```bash bd list --ready --type=bug --priority-max=3 ``` 2. **Rank by priority**: P0 > P1 > P2 > P3 (highest priority bug first, P4 excluded) 3. **Auto-select and start** the top-ranked bug 4. **Continue fixing bugs** if the completed bug was minor: - After completing a bug fix, assess if it was minor (small change, localized fix) - If minor AND there's remaining context (related code still fresh), auto-pick the next bug - Continue this loop until: - A bug requires significant work (not minor) - No more ready bugs remain - Context would be lost (unrelated area of codebase) ### Minor Bug Criteria A bug is considered **minor** if: - Fix touches ≤ 3 files - Change is ≤ 50 lines total - No architectural changes required - Fix is localized (single component/module) ### Context Continuity Continue to next bug automatically when: - Next bug is in same or adjacent files - Next bug is in same module/component - Fix for previous bug provides context for next bug Stop and ask user when: - Next bug is in completely different area of codebase - Next bug appears complex (P0/P1 with unclear scope) - 3+ bugs have been fixed in sequence (natural checkpoint) --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/flurdy) — claim your Tome and manage your conversions.