phase-retro-guardrail-tuner

Cluster phase execution issues into actionable patterns and guardrail patches.

Updated Oct 24, 2025
One-click install
npx skills add https://github.com/5hdaniel/Mad --skill phase-retro-guardrail-tuner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-retro-guardrail-tuner
Source: https://github.com/5hdaniel/Mad/tree/main/.claude/skills/agentic-pm/skills/phase-retro-guardrail-tuner
Command: npx skills add https://github.com/5hdaniel/Mad --skill phase-retro-guardrail-tuner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase retrospectives often generate scattered insights; this skill consolidates evidence from a phase into actionable guardrails, templates, and process improvements to reduce recurring friction.

Core Features & Use Cases

  • Identify recurring friction patterns across tasks and phases.
  • Propose concrete guardrail patches, template updates, and task guidelines.
  • Produce a Phase Retro Report, root-cause analyses, and rollout plans for adoption.

Quick Start

Provide a Phase Retro Report and a concrete guardrail patch with rollout plan based on the phase evidence.

Frequently Asked Questions about phase-retro-guardrail-tuner

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

FAQPage Schema
How do I turn phase retrospective insights into actionable guardrails?

To turn phase retro insights into guardrails, you must cluster execution issues from engineer summaries, CI results, and PR outcomes into actionable patterns. This process generates concrete guardrail patches, template updates, and a rollout plan for adoption.

What is pattern mining for process improvement in sprint retrospectives?

Pattern mining for process improvement is the clustering of recurring friction points across tasks and phases into actionable guardrail patches. It consolidates scattered phase evidence into root-cause analyses, template updates, and task guidelines to reduce recurring friction.

How do I create a rollout plan for guardrail patches after a project phase?

You create a rollout plan by consolidating phase execution evidence into a Phase Retro Report and root-cause analyses. The report proposes concrete guardrail patches and task guidelines, which are then structured into a rollout plan for team adoption.

Can I use CI results and PR outcomes to identify recurring friction patterns?

Yes, you can use CI results and PR outcomes to identify recurring friction patterns. The skill analyzes these inputs alongside engineer summaries to cluster phase execution issues, generating a Phase Retro Report with risk-reduction guardrail patches.

What's the best way to consolidate scattered phase learnings into template updates?

The best way to consolidate scattered phase learnings is to cluster execution issues into actionable patterns based on phase evidence. This approach directly translates identified friction into concrete template updates and task guidelines for process improvement.

When do I need a phase retrospective report for risk reduction?

You need a phase retrospective report for risk reduction when scattered insights from sprints or projects must be consolidated. It transforms phase evidence into actionable guardrails and process improvements to prevent recurring friction across teams.