Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Ro Lifecycle And Comeback Control

ASecurity

Run the repair order from open to closed and stop comebacks at the root cause: WIP/RO aging triage (waiting on approval vs parts vs tech), parts staging before dispatch, and comeback grouping by cause (misdiagnosis, workmanship, part quality, incomplete, no-fault). Rework labor is billed at zero. No PII.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agents

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill ro-lifecycle-and-comeback-control --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ro Lifecycle And Comeback Control?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Ro Lifecycle And Comeback Control
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-ro-lifecycle-and-comeback-control/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-ro-lifecycle-and-comeback-control)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: ro-lifecycle-and-comeback-control
description: "Run the repair order from open to closed and stop comebacks at the root cause: WIP/RO aging triage (waiting on approval vs parts vs tech), parts staging before dispatch, and comeback grouping by cause (misdiagnosis, workmanship, part quality, incomplete, no-fault). Rework labor is billed at zero. No PII."
---

# RO Lifecycle & Comeback Control

The repair order is the shop's unit of work and its unit of money. Two things kill margin in its lifecycle: an RO that **sits** (aged WIP no one is moving) and an RO that **comes back** (rework billed at zero that also cost you the customer).

> **Advisory, operations decision-support.** Labor times and benchmark ranges are `[verify-at-use]`. No customer PII — reason in RO status and job flow.

## The RO lifecycle

`open → written up → authorized → dispatched → parts staged → in repair → QC → closed → follow-up`

Every stall maps to an owner. Read WIP by **age and cause**:

| RO is aging because… | Owner | Action |
|---|---|---|
| Waiting on approval | service advisor | Re-contact customer; supplemental authorization |
| Waiting on parts | parts/staging | ETA, sublet, or stage-then-dispatch |
| Waiting on a tech | dispatch | Re-dispatch to skill/availability |
| Done, not invoiced | advisor/cashier | Close and bill (unbilled = financing the customer) |

**The rule:** set a WIP-age threshold that forces action, and triage by cause — not one RO at a time.

## Comeback control (root cause, not blame)

Group every comeback by cause and fix the process that produced it:

| Cause | Root fix |
|---|---|
| Misdiagnosis | Diagnostic process, tooling, information access |
| Workmanship | Skill match / dispatch, QC step, training |
| Part quality | Supplier/matrix tier decision |
| Incomplete repair | Multi-point verification before closeout |
| No-fault (unrelated/expectation) | Write-up clarity, customer communication |

Rework is billed at zero, paid to the tech, and consumes a bay — it erodes the effective labor rate and car count at once. **Stage parts before the job starts** so a parts-hold never becomes a cold-vehicle re-diagnosis.

## Metrics

| Metric | Reads | Note |
|---|---|---|
| Comeback rate | comeback ROs / total ROs | The quiet tax on labor GP `[verify-at-use]` |
| Average RO age (open WIP) | days open, by cause | Aged WIP is stalled cash |
| Parts-hold RO count | ROs blocked on parts | Staging-discipline signal |
| First-time-fix rate | closed-without-return / total | The inverse quality read |

## Anti-patterns

- Re-fixing a comeback without finding why it came back (it returns again).
- Letting the tech who caused a comeback bill the rework as new work.
- Starting a job before parts are staged.
- Reading total WIP without splitting it by stall cause.

## See also

- Traverse the **comeback root-cause triage** tree in [`../../knowledge/auto-repair-shop-decision-trees.md`](../../knowledge/auto-repair-shop-decision-trees.md).
- [`../technician-productivity-and-efficiency/SKILL.md`](../technician-productivity-and-efficiency/SKILL.md), [`../estimate-and-dvi-workflow/SKILL.md`](../estimate-and-dvi-workflow/SKILL.md), [`../../templates/repair-order-workflow.md`](../../templates/repair-order-workflow.md).
- Best practices: [`../../best-practices/a-comeback-costs-you-twice.md`](../../best-practices/a-comeback-costs-you-twice.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →