turn

Coordinates end-to-end ACE work-turn workflow across email inboxes and canopy-web task board with tiered routing and approval gates.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill turn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turn
Source: https://github.com/dimagi-internal/ace/tree/main/skills/turn
Command: npx skills add https://github.com/dimagi-internal/ace --skill turn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ACE requires a consistent, repeatable process to handle all incoming work (emails, task board items) without missing steps or dropping tasks under load, which manual handling cannot guarantee at scale.

Core Features & Use Cases

  • End-to-end turn orchestration: Automates the full work turn workflow from preflight system checks to final close-out reporting, ensuring no steps are skipped.
  • Tiered inbox processing: Triages incoming emails by sender tier (act, correspond, read-only), routes threads to the correct ACE run, and gates all outbound replies for human approval before sending.
  • Continuous improvement tracking: Explicitly checks for new skills created or repeated manual work that should be automated, and files GitHub issues for confirmed defects to improve the ACE system over time.
  • Use Case: When a team member triggers ACE to "do a turn", this skill ensures every inbound email and canopy-web task is processed consistently, all outbound actions are properly approved, and the team gets a full summary of what was handled, what's blocked, and what needs attention.

Quick Start

Trigger ACE to process its full inbound work turn by instructing it to run a turn, and it will automatically handle preflight checks, task board draining, inbox triage, and close-out reporting with all required guardrails.

Frequently Asked Questions about turn

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

FAQPage Schema
How do I automate inbox triage and task board processing without dropping work under load?

Inbox triage and task board processing are automated through end-to-end turn orchestration, applying preflight validation and tier-based routing to prevent dropped work under load. It processes all inbound surfaces consistently and enforces human approval for outbound replies.

What is an ACE work turn and how does it handle inbound email processing?

An ACE work turn is a full workflow cycle that processes inbound emails by routing threads based on sender tiers like act, correspond, or read-only. It manages the entire cycle from preflight checks and task board draining to close-out reporting.

How do I gate outbound replies for human approval during automated email processing?

Outbound reply gating for human approval is enforced automatically during the turn orchestration workflow. All outbound communications are held for review before sending, ensuring no automated replies go out without explicit human approval.

Can I track workflow defects and repeated manual work for continuous improvement?

Continuous improvement tracking is built into the turn workflow, explicitly checking for new skills or repeated manual work that should be automated. Confirmed defects are filed as GitHub issues to optimize the system over time.

Does turn orchestration work for both email inbox and canopy-web task board draining?

Turn orchestration applies to both the email inbox and the canopy-web task board, draining all inbound surfaces during a single work cycle. It validates, triages, and processes tasks across surfaces to ensure no steps are skipped.

What are the limitations of manual inbound work processing compared to a guardrailed turn workflow?

Manual inbound work processing cannot guarantee consistent handling at scale, often missing steps or dropping tasks under load. A guardrailed turn workflow enforces preflight validation, tier-based routing, and approval gating to prevent these failures.