Sync human-edited decision values from Google Docs into YAML configuration files.
npx skills add https://github.com/dimagi-internal/ace --skill decisions-sync
Please help me install this Agent Skill. Skill: decisions-sync Source: https://github.com/dimagi-internal/ace/tree/main/skills/decisions-sync Command: npx skills add https://github.com/dimagi-internal/ace --skill decisions-sync
When operators edit the human-readable decisions Google Doc for an ACE Connect opportunity run, those changes are not automatically reflected in the structured decisions.yaml file that drives subsequent lifecycle phases. This skill bridges that gap to ensure human overrides are honored in future runs.
Use the decisions-sync skill to sync all human-edited decisions from the per-run Google Doc into the corresponding decisions.yaml file for your current ACE opportunity run.
High-intent search queries and answers about installing and using this skill.
To sync human-edited decisions from a Google Doc to a YAML file, this skill diffs the per-run decisions document against the existing decisions.yaml to identify human-made changes. It then updates the structured YAML configuration while preserving original AI defaults and appending new considered options.
ACE Connect preserves AI default values by keeping original entries intact when human overrides are applied. The sync process marks overridden entries with a status and override value, and appends new considered options from the Google Doc to maintain full auditability of all decision modifications.
Yes, you can update run management parameters like beneficiary count or AI confidence thresholds in decisions.yaml after editing the Google Doc. The skill synchronizes these human-edited values so subsequent ACE opportunity runs use the updated parameters instead of original AI defaults.
The best way to track human overrides in structured run configuration is to diff the human-readable decisions document against the existing YAML. This generates a concise summary of all overrides, added options, and unmatched rows so operators can verify changes at a glance.
Google Doc decision edits are not automatically reflected in the structured run state because the human-readable document and the decisions.yaml file driving lifecycle phases are separate. This skill bridges that gap to ensure human overrides are honored in future runs.
Yes, decisions-sync works with per-run ACE Connect opportunity runs without additional dependencies. It requires only the per-run decisions Google Doc and the existing decisions.yaml file to synchronize human-edited decision values into the structured run state.
dimagi-internalRender ACE run decision logs from YAML into formatted Google Docs.
dimagi-internalCreate or reuse Connect programs for ACE opportunities with PDD archetype alignment.
dimagi-internalGrade OCS chatbot transcripts against LLM-as-Judge rubrics.
rsmdtGenerate structured FOCUS/EXCLUDE prompts for coordinating multi-agent task delegation.
