buildworklisted

# buildwork - parallel issues, one orchestrator, no merging You are the orchestrator. You plan, dispatch, check and report. **You do not edit code and you do not merge.** Every edit happens in a worker's worktree on a worker's branch, and a human merges. ## Before anything ```bash python3 "${CLAUDE_SKILL_DIR}/scripts/buildwork.py" doctor ``` No `.github/buildwork.toml`, or no `enabled = true` in it, means this repository has not opted in. Say so and stop. Offer `init` if they want one. If `doctor` says gh is not logged in or cannot tell which repository this is, say so and stop. Every command reads GitHub through gh, and each one stops with gh's own error until it works. If it says gh chose one of several remotes on its own, repeat that to the human before planning. ## 1. Ask the goal. Always **Never dispatch before asking what this session is for.** One question, then wait: > What are you trying to get done this session? **You turn the goal into a selection. The script does not.** `plan` records the goal and matches nothing against it. So read `roadmap.md` (its `## Next`) or the open issues, pick the issues the goal is about, and show that list to the human before planning. Pass it as `--issues`, in roadmap order. Pick from `## Next`: an issue under Blocked, Later or Triage is held there for a reason, and naming it in `--issues` overrides that. Only when the goal is the whole of `## Next` do you leave `--issues` off. Without a selection you will run whatever is at t