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

• rea-analysis-optimization 456,474 ★
  Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserv
• rea-ci-tests-audit 456,474 ★
  Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for s
• diagnosing-bugs 323,337 ★
  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or r
• migrate-to-shoehorn 323,337 ★
  Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, w
• webapp-testing 194,218 ★
  Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend