next-task

Run one unattended IMPLEMENTATION iteration of the autonomous value-creation loop — steward any in-flight PR, fix interrupts (red CI / security / human bugs), or else build ONE queued `idea` issue on a branch off auto-dev and open a PR that squash-merges on green CI. Ideation lives in the next-idea skill; this skill consumes its queue. Use when the user says "次のタスク", "next task", "続きをやって", or wants autonomous progress without specifying what to do.

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• reverse-engineer-anything 456,653 ★
  Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and b
• scaffold-exercises 323,485 ★
  Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use
• wait-what 323,485 ★
  Stop. That last message did not land: re-pitch it.
• template-skill 193,970 ★
  Replace with description of the skill and when Claude should use it.
• ponytail-debt 190,107 ★
  List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing