dev-backloglisted

# Dev Backlog Real job: keep GitHub Issues as task-definition and lifecycle truth while using `backlog/sprints/` only when complex execution needs a shared continuity, progress, or handoff record. README covers install and human quick start. This file is the agent execution contract: mode routing, file roles, must-do steps, and completion criteria. ## Mode Router | User intent | Mode | Completion boundary | | --- | --- | --- | | "where are we?", "orient", "status" | `orient` | Any admitted sprint state is identified; otherwise the next live Issue is named without manufacturing a sprint. | | "create issue", "new issue", "이슈 만들어" | `create` | A GitHub Issue is created and added to an active sprint Plan only when that work was admitted. | | "plan sprint", "make sprint", or complex work with no active sprint | `plan` | One active sprint file exists with Goal and ordered Plan; `objectives:`/`component:` are present only when their backing spec files exist. | | "work #N", "continue", "do next batch" | `work` | Live Issue AC is verified and lifecycle is updated; an admitted sprint is also updated when present. | | "next", "다음 작업" | `next` | The next actionable batch or sprint-planning need is named. | | "sync", "export issue mirrors" | `sync` | A deliberate legacy/rollback export is produced; it is never a prerequisite for work. | | "complete", "close sprint" | `complete` | Sprint/task state is finalized and rediscovery-prone context is promoted. | If `backlog/` does not exist,