One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill launch-retrospective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: launch-retrospective
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/launch-retrospective
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill launch-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns post-launch ambiguity into a structured, evidence-based retrospective that explains what happened during an AEM Edge Delivery Services launch and what to fix next.

Core Features & Use Cases

  • Launch execution evaluation: Assesses go-live checklist completion and compares planned vs. actual timeline to pinpoint schedule and scope deltas.
  • EDS-specific failure pattern analysis: Reviews performance under real traffic, redirect and migration completeness, and common post-launch issues like missed redirects and third-party script regressions.
  • Actionable, shareable report output: Produces a client-friendly retrospective with a launch scorecard, wins/improvement areas, and owned action items with target dates.

Quick Start

Generate a post-launch retrospective for an AEM Edge Delivery Services project by asking: "Analyze our production launch and create a launch-retrospective report covering go-live checklist results, planned vs actual timeline, performance signals, redirect coverage, migration completeness, and lessons learned."

Frequently Asked Questions about launch-retrospective

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

FAQPage Schema
How do I conduct an AEM Edge Delivery Services launch retrospective?▼

An AEM Edge Delivery Services launch retrospective evaluates go-live checklist completion, planned versus actual timelines, and real-world performance outcomes to produce a structured report with wins, improvement areas, and prioritized action items.

What should I include in a post-launch performance analysis for AEM Edge Delivery Services?▼

Post-launch performance analysis should inspect current production state for EDS-specific patterns including redirect coverage, Core Web Vitals degradation drivers, content migration gaps, and third-party script behavior.

When should I run a post-launch retrospective for a domain migration or major release?▼

Run a post-launch retrospective 1-4 weeks after go-live for major releases, domain migrations, problematic launches, and managed-services handoffs to capture lessons learned and corrective actions.

How do I identify content migration gaps and redirect coverage issues after an AEM go-live?▼

Identify content migration gaps and redirect coverage issues by inspecting the current production state after go-live, comparing planned versus actual outcomes, and reviewing real-world traffic patterns.

Can I generate a client-friendly launch scorecard after a problematic EDS launch?▼

Yes, generate a client-friendly retrospective report after a problematic EDS launch that includes a launch scorecard, documented wins, improvement areas, and owned action items with target dates.

Why does Core Web Vitals degradation happen after an AEM Edge Delivery Services launch?▼

Core Web Vitals degradation often happens due to third-party script regressions and content migration gaps that surface under real-world traffic, requiring post-launch inspection to identify specific drivers.