crusty-old-engineer

Name: crusty-old-engineer
Availability: InStock
Author: Microsoft

Evaluate engineering decisions for long-term costs, failure modes, and trade-offs.

10|11|Updated Feb 22, 2026

Search Tags:#architecture #code review #trade-offs #risk analysis #engineering judgment #legacy refactor

Ready to run

npx skills add https://github.com/microsoft/amplifier-bundle-skills --skill crusty-old-engineer-microsoft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: crusty-old-engineer
Source: https://github.com/microsoft/amplifier-bundle-skills/tree/main/skills/crusty-old-engineer
Command: npx skills add https://github.com/microsoft/amplifier-bundle-skills --skill crusty-old-engineer-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate architecture, tooling, refactors, and implementation choices with a skeptical, consequence-focused lens. It is useful when the real question is not "can we do this?" but "what will this cost later?"

Core Features & Use Cases

Grounded judgment: Surfaces hidden costs, failure modes, maintenance burden, and operational risk.
Decision support: Helps compare alternatives for legacy refactors, new frameworks, automation, and system design.
Constructive direction: Gives a viable next step instead of just saying no.
Evidence-linked advice: Prefers primary references and canonical sources when discussing risks or historical failures.
Use case: Review a proposed migration and get a blunt assessment of the technical debt, rollout risk, and safer sequencing.

Quick Start

Ask the crusty old engineer skill to review your proposal and call out the long-term risks, hidden costs, and safest first step.

Frequently Asked Questions about crusty-old-engineer

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

FAQPage Schema

How do I evaluate architecture trade-offs for a legacy refactor?▼

Evaluating architecture trade-offs involves surfacing hidden long-term costs, failure modes, and maintenance burden specific to your legacy refactor. Skeptical, evidence-linked judgment exposes operational risks and provides constructive alternatives with safer sequencing.

What is the best way to review an implementation plan for technical debt?▼

Reviewing an implementation plan for technical debt means applying consequence-focused judgment to expose rollout risks and operational burden. This grounded critique identifies hidden costs and provides a viable next step instead of simply rejecting the proposal.

Can I use engineering judgment to compare tooling choices and framework migrations?▼

You can use engineering judgment to compare tooling choices and framework migrations by applying skeptical, evidence-linked assessment. This decision support mechanism contrasts alternatives to expose long-term maintenance risks and operational failure modes.

How does risk analysis work when debugging system design checkpoints?▼

Risk analysis for system design checkpoints works by applying skeptical judgment to expose failure modes and hidden consequences. It requires grounded critique, constructive alternatives, and primary-source references to make costly trade-offs obvious before implementation.

When do I need a code review focused on long-term consequences?▼

You need a consequence-focused code review when the real question is not whether you can build it, but what it will cost later. It is critical for architecture reviews, legacy refactors, and tooling choices where hidden maintenance burdens matter.

What are the limitations of relying solely on engineering judgment for architecture reviews?▼

The limitation of engineering judgment in architecture reviews is the need for primary-source references to ground the critique. Without evidence-linked analysis, assessing long-term costs, failure modes, and trade-offs risks missing viable constructive alternatives.