iop/agent-ops/skills/project/orchestrate-agent-task-loop/SKILL.md

name	description
orchestrate-agent-task-loop	Operate dependency-ready agent-task work through the authoritative iop-agent task-loop command. Use for task-group inspection, one-pass execution, blocked retry, parity validation, and review handoff.

Orchestrate Agent Task Loop

Purpose

The production task-loop owner is iop-agent task-loop. The command composes the standalone host with the shared runtime and uses the runtime configuration, provider catalog, durable state, workflow projection, review ports, and integration ports already owned by Go. This skill supplies only operator instructions; it does not contain routing, capacity, model, provider, retry, review, or scheduling policy.

The retained reference fixtures and their future deletion gate are described by the checksum-bound S13 parity manifest. They are not an operator entry point.

Inputs

• workspace: trusted repository root containing agent-task/.
• repo_config: repository-owned runtime configuration path.
• local_config: device-owned runtime configuration path.
• provider_catalog: provider catalog path; required for a live pass only.
• task_group: optional exact m- prefixed selected-Milestone group.
• dry_run: inspect the authoritative workflow projection without starting a provider or mutating durable runtime state.
• retry_blocked: request a bounded resume of the explicitly selected blocked scope during a live pass.

Preconditions

• Read the active PLAN and CODE_REVIEW pair for the requested work.
• Confirm the selected task group maps to one enabled registered project.
• Run a dry pass before any live pass.
• Use a current iop-agent binary built from this checkout.
• Keep repository configuration read-only and keep device state in the configured local roots.

Procedure

1. Build the operator binary from the trusted workspace.

   make build-agent
   

2. Inspect one selected group without provider execution. When no runtime configuration is supplied, this is a configuration-free read-only workflow inspection that uses the same Go parser and does not claim live state.

   build/bin/iop-agent \
     --repo-config /absolute/repo-runtime.yaml \
     --local-config /absolute/device-runtime.yaml \
     task-loop --dry-run --task-group m-selected-milestone
   

3. Run one bounded live pass only after the dry output is accepted. The provider catalog is passed explicitly; selection and all continuation decisions remain runtime-owned.

   build/bin/iop-agent \
     --repo-config /absolute/repo-runtime.yaml \
     --local-config /absolute/device-runtime.yaml \
     --provider-catalog /absolute/providers.yaml \
     task-loop --task-group m-selected-milestone
   

4. Retry a drained blocked scope only when the operator has resolved its external condition. This resumes the same authoritative runtime boundary.

   build/bin/iop-agent \
     --repo-config /absolute/repo-runtime.yaml \
     --local-config /absolute/device-runtime.yaml \
     --provider-catalog /absolute/providers.yaml \
     task-loop --task-group m-selected-milestone --retry-blocked
   

5. Validate cutover and fixture-disposal evidence before a review handoff.

   build/bin/iop-agent task-loop parity --disposal-manifest
   make test-iop-agent-parity
   

Result Interpretation

• Exit 0: the bounded pass or read-only inspection completed. A live pass may leave nonterminal work for a later invocation.
• Exit 2: the selected scope is terminally drained with blockers and no runnable work. Report the bounded blocker output; do not fabricate a retry.
• Exit 1: configuration, workflow, or runtime validation failed. Preserve the error evidence and correct the indicated local condition before retrying.

task-loop --dry-run does not construct a provider process. task-loop parity --disposal-manifest validates every retained reference checksum and prints the Milestone-completion deletion gate; it does not delete fixtures.

Review Handoff

• Leave active PLAN and CODE_REVIEW files in place for the review workflow.
• Treat the Go command output and parity target as implementation evidence, not a review verdict.
• Do not create complete.log, archive task files, or update roadmap status from this operator skill.

Prohibitions

• Do not invoke retained reference fixtures as production execution paths.
• Do not copy lifecycle, policy, provider, recovery, review, or integration logic into this skill or a wrapper command.
• Do not infer dependencies from task numbering or write-set overlap.
• Do not treat an exit code or text output as a review PASS.
• Do not delete checksum-bound reference fixtures before the documented Milestone-completion transition.