decisions-render

Render ACE run decision logs from YAML into formatted Google Docs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling structured ACE run decision logs into readable, shareable Google Docs is time-consuming and prone to version control issues, with teams often struggling to find the latest up-to-date decision record for a given run.

Core Features & Use Cases

  • Idempotent Prose Rendering: Automatically converts the structured decisions.yaml log from any ACE run into a formatted Google Doc, clearing and replacing existing content on each invocation to eliminate stale data.
  • Stable Run-Specific URL: Generates one consistent Google Doc link for every run, making it easy to share decision logs with stakeholders without hunting for updated files.
  • Clear Decision Tracking: Each log entry explicitly labels AI-default decisions and human overrides with plain text status lines, so teams can quickly review which choices were automated and which were manually adjusted.
  • Use Case: For ACE project teams running multi-phase Connect opportunities, this skill automatically publishes up-to-date decision logs at the end of each phase so all team members can review overrides and applied decisions in one centralized location.

Quick Start

Use the decisions-render skill to generate an updated prose Google Doc of the latest decisions log for your current ACE run.

Frequently Asked Questions about decisions-render

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

FAQPage Schema
How do I convert a YAML decisions log into a formatted Google Doc?

To convert a YAML decisions log into a formatted Google Doc, this skill automatically renders structured YAML files into shareable Google Docs, clearing and replacing existing content on each invocation to eliminate stale data and version control issues.

How do I generate a stable Google Doc link for ACE run decision logs?

To generate a stable Google Doc link for ACE run decision logs, this skill produces one consistent, idempotent URL per run, ensuring stakeholders can always access the most up-to-date decision record without hunting for updated files.

Can I distinguish AI-default decisions from human overrides in a rendered decisions log?

Yes, you can distinguish AI-default decisions from human overrides in a rendered decisions log because the skill explicitly labels each log entry with plain text status lines, allowing teams to quickly review which choices were automated and which were manually adjusted.

Does this YAML-to-Google-Doc rendering process support idempotent updates?

Yes, this YAML-to-Google-Doc rendering process supports idempotent updates by automatically clearing and replacing existing Google Doc content on each invocation, preventing duplicate entries and ensuring the document always reflects the latest YAML data.

When do I need to publish decision logs for multi-phase ACE Connect opportunity runs?

You need to publish decision logs for multi-phase ACE Connect opportunity runs at the end of each project phase, automatically generating an up-to-date prose Google Doc so all team members can review applied decisions and overrides in one centralized location.