nextlisted

# Next Pick up the next ready ticket and start work. ## Init Run `lit quickstart` if you haven't already. This provides instructions for using the work tracking system. If the user provided specific information (e.g., a ticket id or area of the codebase to work on), SKIP THE REST OF THESE INSTRUCTIONS and follow the guidance from `lit quickstart` to follow the user instructions. The following information is for determining which work to pick when the user did not specify. ## Finding work Which command answers which question is the quickstart's job — run `lit quickstart work` for that reference. This skill covers only the procedure: the sequence of checks before pulling fresh work (uncommitted changes, open PRs, orphans), what `lit next`'s pick means, and how to work a ticket once you hold one. Now you need to decide whether you need to wrap up in-progress work or start new work. ### In progress work If there are uncommitted changes or open PRs in the repo, we want to wrap these up before starting new work. #### Uncommitted changes determine if these changes are related to a backlog item. If so, that is your current ticket. If not, stop and think to your self: Are these changes worthwhile? Accidential? Incidental? Should we commit or discard them? Use your brain to think about the right solution because there is no one size fits all rule. Examples: - uncommitted pnpm lockfile update: check it out to discard, but then regengerate the lockfile as part of you