origin-ws-loop

Autonomously drains a repository's workstream queue until human input is required.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Aki2022/skills --skill origin-ws-loop-aki2022
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: origin-ws-loop
Source: https://github.com/Aki2022/skills/tree/main/origin-ws-loop
Command: npx skills add https://github.com/Aki2022/skills --skill origin-ws-loop-aki2022

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Processing a backlog of queued workstreams one by one requires constant human supervision. This Skill runs the entire queue in a single unattended loop, executing each workstream, merging green PRs under a continuous-delivery policy, and stopping only when a genuine human question arises. ## Core Features & Use Cases - Autonomous queue draining: Selects the next startable workstream by recorded issue-level runnability, executes it via origin-goal, and closes it via origin-close-session with independent review before autonomous merge. - Bounded review shelf: Parks finished-but-unreviewed workstreams on a capped shelf (default 3) reconstructed from open PRs, so human review is batched instead of interrupting the run. - Safety-first stop discipline: Distinguishes question gates (stop the whole loop) from review gates (shelve and continue), files improvement observations as issues, and produces a final digest including skipped steps and shelf state. - Use Case: After mass-creating workstreams with origin-grill and origin-doc-update, invoke the loop to process the entire backlog overnight, then review one digest and one batch of shelved PRs in the morning. ## Quick Start Run the origin-ws-loop skill on this repository to drain all active workstreams until a human question comes up.

Frequently Asked Questions about origin-ws-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I process multiple workstreams autonomously in one run?

Invoke the loop after stocking the queue with origin-grill and origin-doc-update. It selects each startable workstream by issue-level runnability, executes it via origin-goal, merges green PRs under the CD policy, and stops at the first human question.

What prerequisites does an autonomous workstream loop need?

The repository must have docs governance: docs/00_index.md plus docs/workstreams/ with recorded runnability, authorization envelopes, and merge policies. Without governance the skill refuses to run and reports what is missing instead of creating workstreams itself.

Can the loop merge pull requests without human approval?

Yes, under the default continuous-delivery merge policy, but only after an independent fresh-context reviewer executes the recorded quality gates in an isolated git worktree and returns evidence. Workstreams marked human-gated go to the review shelf instead.

When should I not use the workstream loop?

Do not use it for a single workstream (use origin-goal directly), for creating workstreams or specs (use origin-doc-update or origin-grill), or for recurring scheduled tasks unrelated to workstreams. It only consumes an existing governed queue.

What happens when the loop hits a question or gated issue?

A question gate stops the entire loop after landing already-green work, persisting the exact question in the workstream. A review gate only shelves that one finished workstream, and the loop continues with the next independent ready workstream until the shelf cap is reached.