Next To-Dos
Use when the user asks for the next set of prioritized actions.
Autonomy Routing
This skill produces executable work, not a workflow-selection checkpoint.
After generating todos, if the user selects an item, says to tackle them, or
otherwise signals execution, proceed with the selected or top-priority todo by
default. Do not ask whether to use /goal or direct execution unless
that choice materially changes durability, shared state, safety, or user-visible
behavior.
Trigger
- User asks for "next tasks", "what should I do next", or equivalent planning output.
Workflow
- Inspect context from repo status, recent edits, and user intent.
- Treat planning as read-only. Repository tooling may inform tasks, but its
presence never authorizes mutation or enqueueing.
- Produce a prioritized ordered list of executable tasks.
- Write each item as a full imperative sentence that states a clear objective (e.g. "Add input validation to the /login endpoint so malformed emails are rejected before hitting the database.").
- Start every item with an imperative verb (Add, Fix, Remove, Update, Extract, Replace, Wire, Validate, etc.).
- Each item must be a complete sentence — no sentence fragments, bare noun phrases, or shorthand labels.
- Keep each item to one sentence, 30 words or fewer.
- Make each item specific and testable, with filenames or commands where useful.
- If intent is unclear, ask one focused clarifying question.
- Enqueue only when the user explicitly asks to queue/enqueue the tasks. Route
that separate mutation through the project's queueing or issue-tracking
mechanism; preview keys and summaries, use idempotent adds, and validate
afterward.
Output contract
When intent is unclear, the focused clarifying question in workflow step 9 is
the sole exception to the numbered-list-only output contract; otherwise return
only the numbered list.
- Return only a numbered list.
- Each item is a full imperative sentence starting with a verb, 30 words or fewer.
- No fragments, no bare labels, no shorthand — every item must read as a clear directive.
- No extra commentary outside the list.
1---2name: next-todos3description: Generate imperative next-step to-do lists as full sentences with clear objectives.4---56# Next To-Dos78Use when the user asks for the next set of prioritized actions.910## Autonomy Routing1112This skill produces executable work, not a workflow-selection checkpoint.13After generating todos, if the user selects an item, says to tackle them, or14otherwise signals execution, proceed with the selected or top-priority todo by1516default. Do not ask whether to use `/goal` or direct execution unless17that choice materially changes durability, shared state, safety, or user-visible18behavior.1920## Trigger21- User asks for "next tasks", "what should I do next", or equivalent planning output.2223## Workflow241. Inspect context from repo status, recent edits, and user intent.252. Treat planning as read-only. Repository tooling may inform tasks, but its26 presence never authorizes mutation or enqueueing.273. Produce a prioritized ordered list of executable tasks.284. Write each item as a full imperative sentence that states a clear objective (e.g. "Add input validation to the /login endpoint so malformed emails are rejected before hitting the database.").295. Start every item with an imperative verb (Add, Fix, Remove, Update, Extract, Replace, Wire, Validate, etc.).306. Each item must be a complete sentence — no sentence fragments, bare noun phrases, or shorthand labels.317. Keep each item to one sentence, 30 words or fewer.328. Make each item specific and testable, with filenames or commands where useful.339. If intent is unclear, ask one focused clarifying question.3410. Enqueue only when the user explicitly asks to queue/enqueue the tasks. Route35 that separate mutation through the project's queueing or issue-tracking36 mechanism; preview keys and summaries, use idempotent adds, and validate37 afterward.3839## Output contract4041When intent is unclear, the focused clarifying question in workflow step 9 is42the sole exception to the numbered-list-only output contract; otherwise return43only the numbered list.4445- Return only a numbered list.46- Each item is a full imperative sentence starting with a verb, 30 words or fewer.47- No fragments, no bare labels, no shorthand — every item must read as a clear directive.48- No extra commentary outside the list.
rahulrajaram