skills.rest
shaul1991
shaul1991COMMUNITY
Explore all skills by this author →
WebsiteGitHub

08-maintenance

Orchestrate post-release maintenance workflows with monitoring reports and incident postmortems.

Updated Apr 27, 2026
Search Tags:#monitoring#retrospective#maintenance#governance#kpi#lifecycle-management#incident-postmortem
One-click install
npx skills add https://github.com/shaul1991/shaul-plugin --skill 08-maintenance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 08-maintenance
Source: https://github.com/shaul1991/shaul-plugin/tree/main/claude-code-plugin/project-lifecycle/skills/08-maintenance
Command: npx skills add https://github.com/shaul1991/shaul-plugin --skill 08-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Phase 8 focuses on operational stability after release by guiding monitoring, incident analysis, and retrospectives to drive continuous improvement.

Core Features & Use Cases

  • Governance-driven maintenance rituals including production monitoring, RCA templates, lessons learned, and debt tracking.
  • Structured execution workflow (Plan → Review → Execute → Re-verify) to ensure disciplined post-release activity across teams and branches.
  • Centralized artifact generation and references stored under .claude and docs to enable traceability and audits.

Quick Start

Initiate Phase 8 by drafting the governance plan and creating the initial monitoring report at .claude/08-maintenance/monitoring-report.md.

Frequently Asked Questions about 08-maintenance

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

FAQPage Schema
How do I conduct an incident postmortem for production stability?▼

Production monitoring tracks system health through structured reports stored as artifacts. It applies a governance-driven workflow to review metrics, detect anomalies, and maintain operational stability across active branches.

What is the structured workflow for post-release maintenance and retrospectives?▼

Post-release maintenance follows a Plan, Review, Execute, and Re-verify workflow. This lifecycle management process guides monitoring, feedback analysis, and retrospectives to ensure disciplined continuous improvement.

How do I track technical debt and lessons learned during governance reviews?▼

Governance reviews track technical debt and lessons learned through centralized artifact generation. Records are stored under dedicated directories to enable traceability, satisfy audit requirements, and document retrospective insights.

Do I need specific dependencies to automate incident postmortem workflows?▼

Incident postmortem workflows require no external dependencies. The lifecycle management process uses internal reference components to orchestrate root cause analysis, generate monitoring reports, and satisfy documentation requirements.

What's the best way to establish KPI monitoring reports for continuous improvement?▼

Establishing KPI monitoring reports involves drafting a governance plan and creating initial monitoring documentation. This centralized approach enables feedback analysis, tracks metrics, and drives continuous improvement workflows.

Related Skills

Explore More Product & Management Skills→
him55710-sudohim55710-sudo

benchmark

Measure page performance metrics and compare them against baselines to detect regressions.

Community
Advanced
JeremyDev87JeremyDev87
31

tech-debt

Identify, prioritize, and plan technical debt resolution with ROI-based paydown steps.

Community
Advanced
MissTullyMissTully

canary

Monitor live apps via periodic screenshots and baseline comparisons.

Community
Advanced
1479089714790897
7

kwp-engineering-incident-response

Manage incident response lifecycle with triage, status updates, and postmortem generation.

Community
Advanced