nextlisted

# Route the Workflow This skill is the model-invoked router for the engineering flow. Inspect the current state and return one recommendation. Leave the repository and issue tracker unchanged. ## 1. Refresh the durable state Locate `docs/agents/issue-tracker.md`. If the repository has not been configured for these skills, make `/setup-git-loopy-skills` the sole candidate. Otherwise read the file and refresh the workstream referenced by the conversation from its configured tracker: issue or PR state, labels, assignees, comments, sub-issues, and blockers. Inspect the local branch, commits, and diff when review or publication may be next. When the conversation names no workstream, review the open workflow-bearing issues and their relationships to find the active maps, specs, tickets, and PRs. Use live records rather than session summaries because concurrent sessions may have changed them. Then account for what is already **in flight**, which no tracker records: the worktrees (`git worktree list`), the uncommitted files in each, and the runner or agent process holding one. A git-loopy run names the issue it bound in the newest `.git-loopy/logs/` file and works in the worktree it was started from. Work recommended into a directory another agent is writing collides with it. This step is complete when every candidate action has current state and blocker information from its durable source, and every worktree is accounted for by the process that holds it. ## 2. Find the earlie