worker

The worker skill acts as an autonomous engine within the ERNE ecosystem, designed to bridge the gap between project management platforms and code execution. It is intended for software engineers and teams leveraging AI agents to accelerate feature delivery or maintenance tasks. By polling issue trackers such as ClickUp, GitHub, Linear, Jira, or local JSON files, the worker initiates a sophisticated, multi-stage CI/CD-style pipeline that processes tickets from initial assessment to final code contribution.

• Automated Pipeline Integration: Executes the full ERNE lifecycle including validation, context resolution, planning, execution via Claude Code, testing, self-review, and PR generation.

• Multi-Provider Compatibility: Seamlessly integrates with ClickUp, GitHub, Linear, and Jira via API tokens and configurations, supporting custom filters and polling intervals.

• Intelligent Workflow Management: Utilizes a confidence scoring mechanism to estimate the likelihood of autonomous success before proceeding with code generation.

• Safety and Quality Gates: Enforces ERNE coding standards through automated self-reviews and health delta comparisons, ensuring project audit integrity before any PR is opened.

• Isolated Execution Environments: Operates within isolated git worktrees to maintain repository stability and prevent conflicting changes during autonomous execution.

• Configuration and Usage: Managed via a worker.json file where users define the provider credentials, repository paths, hook profiles, and quality gate thresholds.

• Modes of Operation: Supports continuous polling for background task execution, a --once flag for single-ticket processing, and a --dry-run option for safety-checking tickets without triggering modifications.

• Prerequisites: Relies on the Claude Code agent harness to perform actual code generation, testing, and file system modifications.

• Best Practices: Always monitor the health delta scores and review PR summaries closely, as the worker is designed to assist rather than replace human oversight in complex architecture decisions.

• Constraints: Requires configured API credentials and a valid git environment; effectiveness is bounded by the project's adherence to the ERNE stack detection and rule templates.