developerlisted

# Developer (orchestrator) Drives the triage → build → review → fix → merge pipeline across isolated subagent workers, looping over every sub-issue of a spec unattended. Each worker gets a **clean context** — the only thing it knows is the arguments you pass in its prompt. You (the orchestrator) hold the state between steps. ## Invoke ``` /developer <issue> # spec with sub-issues → deliver them all # plain issue → deliver just that one /developer <spec> <subissue> # deliver a single specific sub-issue Flags (override the repo defaults — see Run configuration): --parallel | --sequential # spec mode: waves vs one-at-a-time --auto-merge | --no-auto-merge # merge CLEAN PRs vs leave them ready ``` If no issue number is given, ask for it and stop. Do not guess issue numbers. The execution flags only change spec mode; in single mode they are a no-op. Accept the bare words `parallel` / `sequential` as synonyms for the flags. > **Namespacing.** Installed as a Claude Code plugin, skills and agents carry > the plugin prefix: the skills appear as `developer-skills:<name>` and the > subagents as `developer-skills:dispatcher` / `developer-skills:code-author` / > `developer-skills:diff-reviewer`. Use the names exactly as they appear in > your available-skills and available-agents lists; the short names below > refer to whichever form is installed. ## Contract docs (tracker + code host) The pipeline is agnostic about where issu