operations-review

Generates operations retrospective reports with evidence-graded root cause analysis and trackable action items.

187|12|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Luyu2026/Skill-Bible --skill operations-review-luyu2026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: operations-review
Source: https://github.com/Luyu2026/Skill-Bible/tree/main/general-operations-skills/operations-review
Command: npx skills add https://github.com/Luyu2026/Skill-Bible --skill operations-review-luyu2026

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After an activity, content cycle, project, or quarter ends, teams often write vague summaries without real root causes or follow-through. This Skill turns process records and data into a structured retrospective report where every conclusion has evidence and every action item has an owner and acceptance criteria. ## Core Features & Use Cases - Goal vs. Result Alignment: Builds a comparison table of original targets versus actual outcomes before any analysis begins. - Evidence-Graded Attribution: Applies 5-Why root cause analysis with A/B/C evidence levels (data-supported, strong inference, speculation) so guesses are never presented as facts. - Trackable Action Items: Outputs 3-5 prioritized actions (P0/P1/P2) with type, owner, acceptance criteria, and deadlines. - Use Case: After a campaign underperforms (participation 8w vs. 10w target), paste the process records and metrics to receive a full retrospective report covering conclusions, attribution, lessons learned, and next-step actions. ## Quick Start Ask the AI to use operations-review to turn your activity or project records and data into a retrospective report with root cause analysis and action items.

Frequently Asked Questions about operations-review

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

FAQPage Schema
How do I write an operations retrospective report after a campaign?▼

Provide the campaign's original goals, process records, and result data. The workflow aligns targets versus outcomes, runs evidence-graded root cause analysis, and outputs a report with conclusions, lessons, and 3-5 trackable action items.

What is evidence grading in root cause analysis?▼

Evidence grading labels each cause as A (directly supported by data), B (strong inference from data plus logic), or C (speculation needing verification). This prevents presenting guesses as facts and keeps uncertain items in a to-be-validated section.

Can this handle monthly or quarterly operations reviews?▼

Yes, it supports periodic reviews for content columns, monthly or quarterly operations cycles, and project or experiment retrospectives, in addition to single-activity post-mortems.

What happens if my data is incomplete for a retrospective?▼

Missing information is marked as [to be supplemented] rather than fabricated. The output degrades to a framework plus a checklist of gaps to fill, so conclusions are never invented without data.

When should I not use an operations retrospective workflow?▼

It is not suited for pure data analysis, which belongs to a dedicated data analysis skill, or pure activity planning, which belongs to an activity planner skill. It focuses specifically on reviewing completed work.