rampstackco/claude-skills / skills/content-refresh-system
content-refresh-system
VerifiedSystematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 363 B |
| SKILL.md | skill md | 25.3 KB |
| references/audit-cadence-patterns.md | markdown | 10.2 KB |
| references/common-refresh-failures.md | markdown | 11.5 KB |
| references/effectiveness-measurement.md | markdown | 10.8 KB |
| references/re-promotion-after-refresh.md | markdown | 10.4 KB |
| references/refresh-depth-decision.md | markdown | 10.4 KB |
| references/refresh-execution-patterns.md | markdown | 9.8 KB |
| references/refresh-prioritization-matrix.md | markdown | 11.1 KB |
| references/refresh-signals-checklist.md | markdown | 10.4 KB |
| references/refresh-vs-merge-vs-delete.md | markdown | 10.1 KB |
references/common-refresh-failures.md
View on GitHub# Common refresh failures
Eleven-plus failure patterns with diagnoses and cures. The patterns appear across programs of different sizes, library ages, and editorial team compositions; the underlying causes are rarely about people and almost always about discipline, prioritization, or measurement gaps.
---
## Failure 1: Refresh-everything-on-calendar
**Symptom.** Every piece gets refreshed on a 12-month or 18-month rotation regardless of signals. Editorial capacity is consumed by maintenance work that often was not needed.
**Diagnosis.** The program treats refresh as a calendar event rather than as a signal-driven decision. Pieces that were performing get touched into worse versions; pieces that were decaying are scheduled for refresh whenever their rotation comes up rather than when the decay signals warrant.
**Cure.** Replace calendar-driven refresh with the prioritization matrix and the signal-driven audit cadence. Refresh on signals; leave stable pieces alone.
**Capacity recovery.** Programs that abandon refresh-everything typically recover 30-50% of their refresh capacity for higher-value work or for new production.
---
## Failure 2: Set-and-forget
**Symptom.** The team has not touched the library in 18+ months. Traffic has eroded across the library; the team is uncertain how much loss is from refresh failure vs other causes.
**Diagnosis.** The program lacks both audit cadence and continuous monitoring. Decay accumulates silently because no system is detecting it.
**Cure.** Establish the hybrid audit pattern: quarterly audit plus continuous monitoring. The first audit will surface a large queue (typical when starting from set-and-forget); the queue should be triaged by the prioritization matrix and worked through over multiple quarters rather than tackled all at once.
---
## Failure 3: Refresh that should have been merge or delete
**Symptom.** The team spends hours refreshing pieces that even at their best will not produce meaningful recovery. The same pieces appear in queue across multiple audits.
**Diagnosis.** The disposition decision was wrong. Refresh was the default disposition because it felt less destructive than merge or delete; the actual right disposition was merge into a stronger sibling or delete with redirect.
**Cure.** Make merge and delete first-class dispositions in the audit. Every piece in the audit gets one of: refresh, merge, delete, monitor, no action. Train the audit owner on the disposition decision flow (see `refresh-vs-merge-vs-delete.md`).
---
## Failure 4: Unprioritized refresh queue
**Symptom.** The refresh queue is 200 pieces deep and growing. The team works through the queue in order of arrival or in order of "easiest first" rather than by value.
**Diagnosis.** No prioritization matrix is being applied. Every piece showing any signal goes in the queue regardless of value.
**Cure.** Apply the 2x2 matrix (value × traffic state). Queue entries get tagged by quadrant. Work focuses on high-value-decaying first; low-value-decaying gets disposition decisions (often merge or delete) rather than refresh; stable quadrants get monitor or no action.
---
## Failure 5: Refresh-on-stable-piece regression
**Symptom.** A flagship piece was performing well. The team refreshed it because it was the next piece in the rotation. After the refresh, traffic dropped 30% and rankings dropped 5 positions.
**Diagnosis.** Refresh-everything-on-calendar damaged a stable piece. The refresh introduced changes that shifted the SERP signals or the piece's structural fit; the new version performs worse than the original.
**Cure.** Stop refreshing high-value-stable pieces by default. Pieces in this quadrant get monitor disposition unless content drift is severe enough to warrant the regression risk. When refreshing a stable piece is genuinely warranted, plan for fast revert if regression occurs.
**Recovery.** Some refresh regressions can be partially reversed by going back to a closer-to-original version of the piece. Some cannot. The lesson informs future stable-piece refresh decisions.
---
## Failure 6: Capacity overcommitment
**Symptom.** The team is exhausted from refresh work. New-piece production is suffering. The team complains of refresh fatigue.
**Diagnosis.** Capacity allocation to refresh is too high (or new-production commitments are too high; the result is the same). The team is being asked to do more total work than capacity allows.
**Cure.** Right-size the allocation. Reduce refresh queue intake by tightening prioritization (only highest-value items enter the queue); or reduce new-production commitments; or temporarily increase capacity. The status quo is unsustainable.
**Sustainability check.** Capacity is real. Programs that pretend capacity is infinite produce burnout, quality drift, and team turnover. The capacity audit (see `refresh-execution-patterns.md`) is what catches this before burnout.
---
## Failure 7: Effectiveness invisible
**Symptom.** "We do not know if our refreshes are working." Refresh work happens but its effectiveness is not tracked or reviewed.
**Diagnosis.** No per-refresh tracking is in place. The program runs without learning data.
**Cure.** Establish the minimum log (see `effectiveness-measurement.md`). Backfill the log for recent refreshes if possible. Establish 30-day and 90-day measurement windows. Run quarterly pattern-detection reviews.
**Adoption.** Logging adds overhead. Programs that resist logging often discover later that the program's effectiveness has been declining for quarters and they cannot tell why because the data was not captured. The overhead of logging is small compared to the cost of running the program blind.
---
## Failure 8: Inconsistent refresh attention
**Symptom.** Some pieces always get refreshed; others never do. The pattern correlates with which writers prefer which topics, not with which pieces need refresh most.
**Diagnosis.** The signal triage is informal and inconsistent. Pieces are getting attention because they are visible to certain people, not because they are most decayed.
**Cure.** Formalize the audit so signal detection is data-driven rather than memory-driven. The matrix and the audit log force visibility on the whole library, not just on the pieces individual team members happen to think of.
---
## Failure 9: Refresh-without-re-promotion
**Symptom.** Refreshes ship. Modified dates update. The team waits for traffic recovery. Recovery is marginal at best. The team concludes refresh does not work.
**Diagnosis.** Re-promotion was skipped. Search engines saw the modified date but audiences did not engage; the recovery curve that re-promotion typically produces did not happen.
**Cure.** Build re-promotion into the workflow as a non-skippable step. Match re-promotion intensity to refresh depth (see `re-promotion-after-refresh.md`). The refresh is not "done" when published; the refresh is "done" when re-promotion has executed.
---
## Failure 10: Audit without follow-through
**Symptom.** The team runs the quarterly audit; produces a queue; the queue largely sits unworked; the next quarter's audit shows the same pieces in queue.
**Diagnosis.** No owner-of-owners is keeping the queue moving. The audit becomes a documentation exercise rather than a refresh-driving exercise.
**Cure.** Assign an owner-of-owners role for the refresh program as a whole. Their job is queue movement, escalation of stalled refreshes, and program-level reporting. Without this role, even good audits do not produce execution.
---
## Failure 11: Quarterly cadence too slow for sharp decay
**Symptom.** The quarterly audit catches a piece in significant decay. The traffic loss has been accumulating for 75 days before the audit caught it. The recovery is harder because the decay has compounded.
**Diagnosis.** Quarterly cadence alone is missing sharp decay. The lag between decay and detection is too long.
**Cure.** Add continuous monitoring for traffic-decay and ranking-drop thresholds. Sharp decay alerts route to fast-track triage; the quarterly audit focuses on slower signals that continuous monitoring cannot detect (content drift, factual staleness, SERP intent shift).
---
## Failure 12: Refresh in isolation when hub orchestration changed
**Symptom.** Pieces are refreshed individually but the hub-level architecture also needed updating. The refreshes ship; the hub-level decay continues because the architecture problem was unaddressed.
**Diagnosis.** Piece-level refresh is being done without coordination with hub-level architecture. Some refresh queues need to escalate to structural-redesign disposition rather than be addressed at piece level.
**Cure.** Coordinate with `pillar-content-architecture` discipline. When piece-level refresh is bumping against architecture-level issues, escalate to a structural-redesign project. Some refresh attempts cannot succeed without the hub-level work.
---
## Failure 13: Stalled refreshes accumulating
**Symptom.** The refresh queue contains zombie items: pieces assigned months ago that have not shipped and are not progressing. Everyone knows they are stalled; nobody is removing them.
**Diagnosis.** No stalled-refresh recovery process. Refreshes that get stuck stay stuck because there is no review mechanism to escalate or reassign.
**Cure.** Build stalled-refresh review into each quarterly audit. Refreshes that have been in queue more than two cycles get reviewed: reassign owners, re-scope depth, or remove from queue if the disposition was wrong. The review prevents zombie accumulation.
---
## Failure 14: Light-edit-as-default
**Symptom.** Most refreshes are light edits regardless of signal strength. The light edits do not move the needle on pieces that needed substantial revision; the team concludes "refresh does not work" when the actual issue is depth mismatch.
**Diagnosis.** Depth assignment is defaulting to light edit because light edits are the easiest to schedule. Substantial revision and full rewrite are being skipped because they are harder to fit into capacity.
**Cure.** Match depth to signal strength explicitly. Depth-light when signals support light edit; depth-deeper when signals warrant. Capacity allocation should account for depth distribution; if the team consistently has capacity only for light edits, the allocation needs adjustment, not the depth assignment.
---
## The cross-cutting pattern
Most refresh failures share a single root: shortcuts in discipline. Calendar-refresh shortcuts the signal analysis. No-measurement shortcuts the learning. Refresh-as-default shortcuts the disposition decision. Light-edit-as-default shortcuts the depth decision. No-re-promotion shortcuts the audience-engagement work. Each shortcut feels like it is saving capacity; each shortcut is actually shifting capacity to lower-value work.
The fix for almost any refresh failure is the same: surface the discipline that was being shortcutted, and pay the cost of running the discipline. The capacity recovered from eliminating low-value refreshes typically more than pays for the discipline overhead.
---
## Methodology-level choices that stay in the public skill
The fourteen failure patterns with diagnoses and cures, the cross-cutting pattern that connects most of them, the discipline-as-cure observation.
## Implementation choices that stay internal
Specific tooling for stalled-refresh detection. Specific reporting templates for owner-of-owners updates. Specific reviewer training on disposition decisions. Specific automation that catches refresh-without-re-promotion. The team's own conventions for capacity recalibration when overcommitment is detected. These vary by team, tooling, and program structure.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |