crusty-old-engineer

Identify long-term consequences, hidden costs, and failure modes of architectural decisions.

8|4|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rysweet/amplihack-rs --skill crusty-old-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crusty-old-engineer
Source: https://github.com/rysweet/amplihack-rs/tree/main/amplifier-bundle/skills/crusty-old-engineer
Command: npx skills add https://github.com/rysweet/amplihack-rs --skill crusty-old-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Addresses the risk of poorly planned architectures by surfacing long-term consequences, hidden costs, and governance gaps early.

Core Features & Use Cases

  • Grounded Skepticism: routinely questions assumptions, identifies hidden costs, and surfaces historical failure modes.
  • Constructive Progress: provides viable forward paths, safer first steps, and explicit trade-offs.
  • Evidence-Linked Judgment: anchors recommendations to primary sources and concrete data.
  • Use Cases: architectural decisions, legacy refactors, tooling evaluations, and broad planning questions.

Quick Start

Describe your architectural decision and ask COE to provide a risk-aware evaluation.

Frequently Asked Questions about crusty-old-engineer

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

FAQPage Schema
How do I identify hidden costs and long-term consequences of an architectural decision?

To identify hidden costs in an architectural decision, apply grounded skepticism to question assumptions and surface historical failure modes, providing explicit trade-offs and viable forward paths.

What is the best way to evaluate risks when planning a legacy refactor?

The best way to evaluate risks during a legacy refactor is to apply evidence-linked judgment, anchoring recommendations to primary sources and concrete data to establish safe first steps and guardrails.

How do I perform a skeptical design review for new tooling evaluations?

A skeptical design review for new tooling evaluates governance gaps and failure modes, demanding evidence-linked judgment to construct explicit trade-offs and safer first steps before adoption.

Can I use this approach to find guardrails for broad architectural planning in complex systems?

Yes, you can use this approach to establish guardrails for broad architectural planning in complex systems by surfacing long-term consequences and anchoring recommendations to concrete data.

When should I not use evidence-linked judgment for architectural evaluations?

You should not use evidence-linked judgment when primary sources or concrete data are unavailable, as recommendations require explicit trade-offs and references to properly assess failure modes.

Does risk-aware architectural evaluation work without explicit trade-offs?

No, risk-aware architectural evaluation does not work effectively without explicit trade-offs, as identifying failure modes and hidden costs demands viable forward paths and evidence-linked judgment.