candidate

Enqueue work items as candidate sets and activate them for validation.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ether-moon/agent-atelier --skill candidate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: candidate
Source: https://github.com/ether-moon/agent-atelier/tree/main/plugins/agent-atelier/skills/candidate
Command: npx skills add https://github.com/ether-moon/agent-atelier --skill candidate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Candidates bridge implementation and validation. When a builder finishes work items, they are enqueued as a candidate set — one or more WIs sharing a branch and commit. The orchestrator activates the next set into the exclusive validation slot (one at a time). After validation, the set is cleared as completed or demoted (fate-sharing: all WIs succeed or all return to rework).

Core Features & Use Cases

  • Enqueue one or more WIs as a candidate set for validation. For batch enqueue, provide comma-separated WI IDs.
  • Activate the next queued set for validation, ensuring a single active slot and FIFO ordering.
  • Clear after all WIs pass or after failure, applying fate-sharing and updating statuses and promotion metadata.

Quick Start

Enqueue WI-014 after implementing it to place the item into the candidate queue.

Frequently Asked Questions about candidate

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

FAQPage Schema
How do I manage work-item validation pipelines with batch promotion?

Batch promotion in validation pipelines queues WIs as a candidate set, activates them one at a time, and clears them with transactional updates. Fate-sharing ensures all WIs succeed or return to rework together.

What is fate-sharing in a candidate validation workflow?

Fate-sharing in candidate validation means all WIs in a batch succeed or fail together. When clearing the validation slot, the entire set is marked completed or demoted to rework, enforcing atomic batch consistency.

How do I enqueue multiple work items for validation?

To enqueue multiple WIs for validation, provide comma-separated WI IDs. The orchestrator groups them into a candidate set sharing a branch and commit, then activates the set for validation using FIFO ordering.

Can I activate multiple work-item sets for validation at the same time?

You cannot activate multiple WI sets simultaneously. The pipeline enforces a single active validation slot, ensuring only one candidate set is validated at a time while others wait in the queue.

What happens to a candidate set when validation fails?

When validation fails, the candidate set is demoted back to rework. Due to fate-sharing, all WIs in the batch return together, and the validation slot is cleared so the next queued set can be activated.