pm-auditor

Detect stale downstream features, epics and tests via base_version tracking and cascade analysis.

Updated Oct 17, 2025
One-click install
npx skills add https://github.com/x85446/claudecodetricks --skill pm-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-auditor
Source: https://github.com/x85446/claudecodetricks/tree/main/skills/pm-auditor
Command: npx skills add https://github.com/x85446/claudecodetricks --skill pm-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect when upstream changes invalidate downstream work and identify cascading impacts across features, epics, and tests using a base_version tracking system.

Core Features & Use Cases

  • Detects stale features, requirements, and tests based on version differences
  • Analyzes cascade effects across epics and their dependent work
  • Provides actionable remediation guidance to restore consistency after upstream changes

Quick Start

Run /pm-auditor myriplay stale to identify all downstream entities affected by upstream changes.

Frequently Asked Questions about pm-auditor

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

FAQPage Schema
How do I detect stale downstream features after upstream product changes?

To detect stale downstream features after upstream product changes, use base_version tracking and cascade analysis to identify invalidated requirements, tests, and epics across your release planning model, then review the proposed remediation guidance to restore consistency.

What is upstream downstream dependency cascade analysis in product development?

Upstream downstream dependency cascade analysis in product development is a versioning mechanism that tracks base_version differences to identify when upstream changes invalidate dependent work, flagging stale features and tests across epics to maintain release planning consistency.

How do I track stale requirements and tests across epics using version differences?

Track stale requirements and tests across epics by comparing base_version differences between upstream changes and downstream work, which flags invalidated entities and provides actionable remediation guidance to restore product consistency.

Can I use cascade analysis to flag stale entities for release planning?

Yes, you can use cascade analysis to flag stale entities for release planning by applying base_version tracking to your product development model, identifying invalidated downstream features and tests, and generating remediation proposals to restore consistency.

What's the best way to remediate downstream work invalidated by upstream changes?

The best way to remediate downstream work invalidated by upstream changes is to run a staleness audit using base_version tracking, which reports cascading impacts across epics and proposes actionable guidance to restore product development consistency.