work-issue
claudeWork one GitHub issue: a planner (Opus) first reads it and the code and posts an implementation plan or the open owner questions on the issue, or closes the issue when the owner's answer picks a close option, then the worker implements the current plan to an open pull request, or unsupervised through independent review and merge; an orchestrator runs planner and worker for labelled or named issues and continues issues that are already started (current plan, own pushed branch, own open PR) until they are merged; a skill proposes the opt-in label per issue and sets it on confirmation.
4 skills · 2 agents