skills.rest
outfitter-dev
outfitter-devOFFICIAL
Explore all skills by this author →
Website𝕏@outfitter_devGitHub

upstream-evaluation

Evaluate upstream changes against Navigator design frameworks for adoption decisions.

2|Updated Jan 14, 2026
Search Tags:#software-engineering#change-management#navigator#decision-frameworks#upstream-evaluation#adopt-skip-adapt
One-click install
npx skills add https://github.com/outfitter-dev/navigator --skill upstream-evaluation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upstream-evaluation
Source: https://github.com/outfitter-dev/navigator/tree/main/.claude/skills/upstream-evaluation
Command: npx skills add https://github.com/outfitter-dev/navigator --skill upstream-evaluation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic evaluation of upstream changes using Navigator's design frameworks to decide what to adopt, skip, or adapt.

Core Features & Use Cases

  • Structured evaluation process that categorizes upstream changes by type and applies a decision framework to determine the optimal outcome.
  • Documentation of decisions, naming conventions, and potential schema considerations to support downstream implementation and handoff.
  • Use cases include evaluating feature proposals, API changes, and vendor adaptations to ensure alignment with Navigator principles.

Quick Start

Analyze a provided upstream change and generate a decision package with recommended actions and rationale.

Frequently Asked Questions about upstream-evaluation

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

FAQPage Schema
How do I decide whether to adopt, skip, or adapt upstream changes in my codebase?▼

To decide whether to adopt, skip, or adapt upstream changes, you evaluate them against design frameworks to determine the optimal outcome, enforcing categorization and naming checks to ensure consistency with existing concepts.

What is the best way to evaluate upstream API evolutions for internal forks?▼

Evaluating upstream API evolutions for internal forks requires applying a structured decision framework to categorize changes, check naming conventions, and document potential schema considerations for downstream implementation.

Can I use this evaluation process for feature proposals as well as codebase changes?▼

Yes, the upstream evaluation process applies to feature proposals, API changes, and codebase changes across internal forks, ensuring alignment with existing design principles and consistency with current concepts.

How does the change management framework handle documentation and handoff for upstream decisions?▼

The change management framework handles documentation and handoff by generating a decision package with recommended actions, rationale, and naming conventions, producing outputs suitable for downstream implementation.

When should I adapt an upstream change instead of fully adopting it?▼

You should adapt an upstream change instead of fully adopting it when the change requires modifications to maintain consistency with existing concepts, naming conventions, and design frameworks within your internal codebase.

Related Skills

Explore More Software Engineering Skills→
deepeshBodhdeepeshBodh
35

analysis-codebase

Analyze codebases to extract tech stack, patterns, and collision risks.

Community
Advanced
jankneumannjankneumann

parallel-implement-feature

Execute approved OpenSpec proposals with parallel DAG-scheduled agents.

Community
Advanced
HDeiblerHDeibler
6

consistency-internal

Align components, flows, tokens, and shared vocabulary across product surfaces.

Community
Intermediate
AuroraWebSoftwareAuroraWebSoftware
41

openspec-new-change

Create a new change directory in the OpenSpec framework.

Official
Intermediate