Dev10x:playbook-maintenance

Detect drift between user playbook overrides and default playbooks.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-playbook-maintenance-dev10x-guru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:playbook-maintenance
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/playbook-maintenance
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-playbook-maintenance-dev10x-guru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps detect drift in user playbook overrides against current defaults, identifying missing or outdated steps, prompts, and fragments.

Core Features & Use Cases

  • Playbook Drift Detection: Compares user overrides against default playbooks to find discrepancies.
  • Actionable Findings: Provides a detailed report with recommendations for resolving drift.
  • User-Driven Actions: Allows users to review and apply suggested changes or export a report for later review.

Quick Start

To check for drift in your playbook overrides, use the command /Dev10x:playbook-maintenance.

Frequently Asked Questions about Dev10x:playbook-maintenance

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

FAQPage Schema
How do I detect drift between my playbook overrides and default playbooks?

To detect playbook drift, you can compare user overrides against default playbooks using YAML parsing to identify missing steps, improved prompts, and structural changes. This analysis generates a detailed report with actionable recommendations for resolving discrepancies.

What is playbook drift and how does YAML parsing identify missing steps?

Playbook drift occurs when user overrides become outdated compared to default playbooks. YAML parsing analyzes orchestration steps and structural changes to identify missed updates, new steps, or improved prompts that the user overrides lack.

How do I automate playbook maintenance and check for structural changes?

You can automate playbook maintenance by running a drift detection analysis that orchestrates multiple task steps. It compares your overrides against defaults to find structural changes and outputs a report for review or export.

Can I export a playbook drift report for later review instead of applying changes immediately?

Yes, after analyzing playbook drift, you can choose to export the detailed findings report for later review rather than applying the suggested changes immediately. This allows for user-driven action based on the detected discrepancies.

What is the best way to find outdated prompts in my playbook overrides?

The best way to find outdated prompts is through playbook drift detection, which compares your overrides against current defaults. This analysis identifies improved prompts and structural changes missed by your existing overrides.