Validate UAT sign-offs and QA verdicts before activating Connect opportunities.
npx skills add https://github.com/dimagi-internal/ace --skill llo-launch-dimagi-internal
Please help me install this Agent Skill. Skill: llo-launch Source: https://github.com/dimagi-internal/ace/tree/main/skills/llo-launch Command: npx skills add https://github.com/dimagi-internal/ace --skill llo-launch-dimagi-internal
Manually coordinating the go-live process for Connect opportunities is high-risk and time-consuming, as it requires verifying multiple QA gates, archetype-specific UAT sign-offs, and sending tailored notifications to LLOs, all while maintaining auditable records for compliance.
Use the llo-launch skill to activate your named Connect opportunity for go-live once all UAT sign-offs and deep QA verdicts are confirmed and up to date.
High-intent search queries and answers about installing and using this skill.
Automating Connect opportunity activation requires verifying UAT sign-offs and fresh deep QA verdicts. The process validates archetype-specific readiness checks, updates run state YAML, and sends tailored LLO notifications to enable live production use.
Focus-group opportunity go-live requires confirming Session 1 logistics are locked and validating that deep QA verdicts are not stale. The system checks these archetype-specific gates before activating the opportunity and sending LLO launch notifications.
UAT verification for multi-stage archetypes validates tailored readiness gates and stage transition timelines. The process halts activation if blockers are found, ensuring all UAT sign-offs and deep QA verdicts are confirmed before live production use.
Operator overrides are allowed during opportunity activation but are fully logged for compliance audit trails. The system maintains structured launch records and updates run state YAML to ensure full traceability of all go-live decisions.
When deep QA verdicts are stale, the activation process halts to prevent go-live. Fresh deep QA verdicts must be obtained against current builds before the system can proceed with validating readiness gates and sending LLO notifications.
LLO notifications must be archetype-specific to include relevant launch details like app URLs for atomic-visit, session schedules for focus-group, or stage transition timelines for multi-stage opportunities, eliminating manual outreach errors.
jjacksonAutomate CRISPR opportunity go-live by coordinating UAT sign-offs and Connect activation.
solatisOptimize Claude Code agent system prompts through phased analysis and human approval.
exiaoAutomate App Store Connect operations via the asc CLI for releases, TestFlight, and submissions.
jjacksonCollect LLO feedback and document responses in ACE closeout files.
