upstream-fix

Trace quality failures to root causes in specs, rules, or workflows.

Updated Mar 10, 2026

Search Tags:#workflow #remediation #quality #spec #root-cause #upstream #rule

Ready to run

npx skills add https://github.com/iamsteveholmes/momentum --skill upstream-fix-iamsteveholmes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: upstream-fix
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/upstream-fix
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill upstream-fix-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traces quality failures upstream to their root cause in specs, rules, or workflows, and proposes fixes at the right level.

Core Features & Use Cases

Root-cause tracing: Identify whether issues originate in specs, rules, or workflows.
Upstream remediation proposals: Suggest fixes at the appropriate abstraction level to reduce rework.
Workflow integration: Integrates into existing QA and review processes to improve feedback loops.

Quick Start

Invoke the upstream-fix skill during a quality failure review to begin tracing and proposing upstream fixes.

Frequently Asked Questions about upstream-fix

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

FAQPage Schema

How do I trace quality failures upstream to their root cause?▼

Root-cause tracing identifies whether quality failures originate from specs, rules, or workflows. By analyzing post-failure data, it categorizes the exact origin point and proposes remediation at the correct abstraction level.

What is the best way to propose upstream fixes for workflow defects?▼

Proposing upstream fixes involves suggesting corrections at the appropriate abstraction level within specs, rules, or workflows. Integrating this analysis into existing QA processes improves feedback loops and reduces future rework.

When do I need to analyze specs and rules for post-failure remediation?▼

You need post-failure remediation when a quality failure occurs and you must determine if the root cause lies in specs, rules, or workflows. This tracing targets the exact process level where the defect originated.

Can I integrate root-cause analysis into my existing review processes?▼

Yes, root-cause analysis integrates into existing QA and review processes. Applying post-failure tracing within your established workflows improves feedback loops and targets remediation at the correct process level.

Why does tracing defects upstream reduce rework in software workflows?▼

Tracing defects upstream reduces rework by pinpointing whether failures originate in specs, rules, or workflows. Fixing the root cause at its exact abstraction level prevents the same defect from recurring downstream.