execute

Name: execute
Availability: InStock
Author: Ether

Coordinate work item claim, heartbeat, requeue, complete, and attempt lifecycles.

Updated Mar 9, 2026

Search Tags:#automation #validation #orchestration #execute #work-item #state-commit #native-task

Ready to run

npx skills add https://github.com/ether-moon/agent-atelier --skill execute-ether-moon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/ether-moon/agent-atelier/tree/main/plugins/agent-atelier/skills/execute
Command: npx skills add https://github.com/ether-moon/agent-atelier --skill execute-ether-moon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates the end-to-end execution lifecycle of work items, enabling deterministic claim, heartbeats, requeues, completion with evidence, and recording attempts to keep the workflow moving and auditable.

Core Features & Use Cases

End-to-end lifecycle management: claim, heartbeat, requeue, complete, and attempt operations with consistent state transitions.
Lease and validation: enforces lease timing and preconditions, then validates completion through evidence and manifests.
Native task synchronization: keeps the system in sync with native tasks while preserving a single source of truth in work-items.json.

Quick Start

Claim a work item to begin implementation, then use heartbeat to maintain the lease and perform requeue, complete, or attempt actions as needed.

Frequently Asked Questions about execute

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

FAQPage Schema

How do I manage work-item execution lifecycles end-to-end?▼

Work-item execution lifecycle management is handled by claiming items, sending heartbeats to maintain leases, and performing requeue, complete, or attempt actions to keep workflows moving and auditable.

What is the best way to orchestrate deterministic state transitions for task execution?▼

Orchestrating deterministic state transitions requires routing all mutations exclusively through a state-commit writer, ensuring consistent updates and a single source of truth in work-items.json.

How does native task synchronization work with a custom work-items.json file?▼

Native task synchronization keeps the system in sync with native tasks while preserving work-items.json as the single source of truth for all execution state and records.

Do I need to validate preconditions and provide evidence for task completion?▼

Yes, task completion requires validating preconditions per subcommand and enforcing lease timing, then validating completion through evidence and manifests before finalizing the state transition.

When should I use heartbeat and requeue operations during work-item orchestration?▼

Heartbeat operations maintain the lease during active execution, while requeue operations return work items to the queue when processing cannot be completed, ensuring workflow continuity.

Can I record multiple execution attempts for a single work item?▼

Yes, recording attempts for individual work items tracks execution history, enabling auditable workflows and providing visibility into retry behavior across the orchestration lifecycle.