keep-the-pool-full

Once implementation, review and merging are automated, the bottleneck moves upstream to supply. Agents with nothing well-defined to pick up either sit idle or invent work. This skill keeps a pool of issues that an agent can take, finish and land on its own: each one is real, independently mergeable, small, checkable and not a duplicate. The human job shifts from "build X" to setting the pool's target and its sources.

When to use

• The count of ready issues is below the target, or will be within a day at current throughput.
• A delivery loop or a set of worker automations reports NOOP(no eligible work) repeatedly.
• On a schedule (daily, or every few hours during an active run).

When not to use

• No one or nothing is consuming the pool. Filing issues nobody picks up is noise.
• The work needs product decisions that haven't been made. File one decision issue for a human instead.
• The repo's maintainers haven't agreed to agent-filed issues. Ask once; on other people's repos default to DRY_RUN.

Steps