sa-balance-guardian

Evaluate proposed solutions for tactical and strategic balance.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/hilaryosborne/skills --skill sa-balance-guardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sa-balance-guardian
Source: https://github.com/hilaryosborne/skills/tree/main/solution-architect/sa-balance-guardian
Command: npx skills add https://github.com/hilaryosborne/skills --skill sa-balance-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that proposed technical solutions strike an appropriate balance between immediate tactical needs and long-term strategic goals, preventing both under-delivery of value and over-engineering.

Core Features & Use Cases

  • Strategic vs. Tactical Evaluation: Assesses whether a solution prioritizes short-term gains at the expense of future maintainability or invests too heavily in future needs not yet realized.
  • ROI and Debt Analysis: Evaluates the business value and return on investment against the technical debt incurred or the potential for over-engineering.
  • Use Case: During a blueprint review, the Balance Guardian skill would analyze a proposed architecture to determine if its complexity is justified by the business problem it solves, or if it's an elegant solution to a problem that doesn't yet exist, or if it's a quick fix that will create significant future debt.

Quick Start

Ask the solution architect to describe the problem, the proposed solution, and the rationale behind it.

Frequently Asked Questions about sa-balance-guardian

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

FAQPage Schema
How do I evaluate technical debt against business value during an architecture review?

To evaluate technical debt against business value, assess the proposed solution's ROI, expected lifespan, and delivery pragmatism to ensure architectural complexity is justified by the actual business problem it solves.

What is over-engineering risk in solution architecture and how is it assessed?

Over-engineering risk in solution architecture is the likelihood of investing heavily in future needs not yet realized; it is assessed by evaluating whether proposed solution complexity actually matches current tactical delivery requirements.

How do I balance short-term tactical delivery with long-term strategic goals?

You balance short-term tactical delivery with long-term strategic goals by assessing proposed technical solutions to prevent both under-delivery of immediate business value and excessive investment in future maintainability.

How do I perform an ROI analysis on a proposed architectural decision?

Perform an ROI analysis on a proposed architectural decision by weighing business value and return on investment against the technical debt incurred, guiding dialogue toward pragmatic and value-driven outcomes.

When should I avoid a quick fix that creates significant future technical debt?

You should avoid a quick fix that creates significant future technical debt when the solution prioritizes short-term gains at the expense of future maintainability without aligning with long-term strategic investment goals.