Select
ProductivityselectSelect is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Explicit-only: pick the next `bd ready` bead via risk-first heuristics; verify dependency/readiness, add missing deps, then mark in progress and comment.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/devops/select-tkersey-dotfiles-d847c98c/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/select, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Select
Intent
Choose the next bead by risk, hardness, and blast radius; gate on codebase readiness and dependencies before marking in_progress; leave a short rationale comment.
Selection rubric
- Feature-first: if any ready items are
feature, evaluate all ready features (bd show). - Type order (fallback):
task>bug>epic>chore. - Priority: P0 > P1 > P2 > P3 > P4.
- Risk: migrations, auth/security, infra, data loss/consistency, breaking API/CLI, perf regressions, ambiguous acceptance.
- Hardness: vague scope, multiple subsystems, unknown deps, heavy verification.
- Blast radius: widely used modules, shared config, CI/build pipeline, core user paths.
- Tie-break: priority → strongest signals → earliest in
bd ready. - Readiness gate: never start a bead if required scaffolding or prerequisites are missing; add deps and restart selection.
Workflow
- Run
bd readyand keep the returned order. - If any ready features exist,
bd show <id>for each and score (risk/hardness/blast). - Otherwise, score ready items by type order and priority.
- Check readiness for the top candidate (repo-only):
- Confirm required scaffolding/infra exists in the repo (app skeleton, build config, migrations, auth setup, etc.).
- If something is missing, look for an existing prerequisite bead and link it first:
- Link:
bd dep add <candidate-id> <dep-id> -t blocks
- Link:
- Only create a new prerequisite bead if none exists:
- Create:
bd create "Scaffold: <thing>" --type=task --priority=<p> - Link:
bd dep add <candidate-id> <dep-id> -t blocks
- Create:
- Re-run
bd readyand restart selection if you added any deps.
- Pick the highest-scored ready bead after the readiness gate passes.
- Mark it in progress:
bd update <id> --status in_progress. - Comment rationale:
bd comments add <id> "Selected first: <short rationale>".
Output
- Print:
Selected <id>: <rationale>. - If
bd readyis empty, report "No ready work" and stop. - If deps were added, print:
Blocked <id> on <dep-ids>; re-run selection.