aops-cli-tasker

Operates AOPS Tasker and Runner CLI commands for DAG-aware execution and worker leases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eeemzs/aops --skill aops-cli-tasker-eeemzs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aops-cli-tasker
Source: https://github.com/eeemzs/aops/tree/main/assets/skills/aops-cli-tasker
Command: npx skills add https://github.com/eeemzs/aops --skill aops-cli-tasker-eeemzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating human-first task execution across DAG-structured work slices is error-prone when agents guess at CLI flags, confuse Tasker WorkGroups with Projectman sprints, or reimplement scheduling logic that the hosted domain service already enforces atomically. ## Core Features & Use Cases - Ownership routing: Directs planning and review to Projectman, human-first execution tracking to Tasker, run/lease control to Runner, and durable memory to Agentspace. - DAG-aware status and planning: Reads ready/waiting/blocked/stalled scheduling state and plans slice dependencies with deterministic topological waves via aops loop parallel-plan. - Atomic worker leases: Previews and applies worker claim/release operations with idempotency keys, letting the domain service enforce readiness, terminal gates, and maxParallelSlices. - Use Case: An agent resuming a multi-slice run checks aops runner status to find the next-ready slice, claims it atomically with a worker lease, and releases the lease with the correct terminal state when finished. ## Quick Start Ask the agent to use the aops-cli-tasker skill to check Runner status for your run ID and claim the next ready slice with an atomic worker lease.

Frequently Asked Questions about aops-cli-tasker

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

FAQPage Schema
How do I claim the next ready task slice with the aops runner?▼

Run aops runner worker claim with the run ID, worker ID, runtime key, and an idempotency key, first with --preview then with --apply. Omit --slice-id for deterministic claim-next, or pass it to claim a specific slice.

What is the difference between aops tasker and aops pm?▼

Projectman (aops pm) handles planning and reviews such as sprints, while Tasker (aops tasker) tracks human-first execution in WorkGroups. A Tasker WorkGroup is an execution batch, not a Projectman sprint.

How do I plan slice dependencies with aops loop parallel-plan?▼

Pass --plan with the sprint ID, one --slice per slice, and --slice-deps mappings like cli=core. The preview rejects unknown, duplicate, self, and cyclic edges and shows deterministic topological waves.

When is a DAG dependency considered ready in the aops runner?▼

A dependency is ready only after the upstream slice reaches the merged state; an accepted state is not sufficient. Check readiness with aops runner status using --include-events and --summary.

Can I implement my own scheduler on top of aops tasker?▼

No. The domain service atomically enforces DAG readiness, terminal and cancel gates, active-slice uniqueness, and maxParallelSlices. Running a second scheduler, DCM, or migration engine from this skill is an explicit anti-pattern.