build-advisor

Diagnose built UI, workflow, spec, or implementation issues with criteria and options.

280|30|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Undertone0809/rudder --skill build-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-advisor
Source: https://github.com/Undertone0809/rudder/tree/main/.agents/skills/build-advisor
Command: npx skills add https://github.com/Undertone0809/rudder --skill build-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Build-advisor helps when something you built (UI, workflow, spec, or implementation) feels wrong or weak, but you cannot clearly articulate what is broken or what the right next move should be.

Core Features & Use Cases

  • First-principles diagnosis and reframing: converts vague dissatisfaction into a clearer problem statement, professional diagnosis, and scenario map.
  • Criteria-first evaluation setup: defines explicit evaluation criteria and a grounded way to judge whether the next iteration is actually better.
  • Actionable options and a decision-ready recommendation: proposes 2-3 realistic options and provides one recommended option plus a concrete next move.
  • Layer identification across teams: determines whether the issue is primarily product framing, UX/information architecture, engineering shape, workflow/process, or observability/evaluation evidence.
  • Routing toward specialized follow-up: recommends when the best next step is to invoke a more specific skill (e.g., design-review, plan-eng-review, investigate, or langfuse).

Quick Start

Ask build-advisor to analyze your build using evidence you have (screenshots, transcript, traces, benchmarks, or artifacts) and produce an evaluation-ready critique with criteria, options, and a recommended next move.

Frequently Asked Questions about build-advisor

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

FAQPage Schema
How do I diagnose why my UI workflow feels wrong but I can't pinpoint the issue?

To diagnose a UI workflow that feels wrong, use first-principles scenario analysis to convert vague discomfort into a clearer problem statement, identify the affected layer, and map requirements. This process reframes fuzzy dissatisfaction into an explicit evaluation rubric.

What is the best way to evaluate a product implementation before the next iteration?

The best way to evaluate a product implementation is establishing criteria-first evaluation. Define explicit evaluation criteria and a grounded rubric to judge whether the next iteration is actually better, ensuring your post-build critique is objective rather than subjective.

Can I get actionable options for fixing a broken design spec?

You can get actionable options for a broken design spec by generating a decision-ready recommendation. This approach provides 2-3 realistic options and a concrete next move, routing toward specialized follow-up skills if deeper diagnosis is required.

How to determine if my build issue is product framing or engineering shape?

To determine if a build issue is product framing or engineering shape, perform layer identification. This diagnosis evaluates whether the problem stems from product framing, UX, engineering shape, workflow process, or observability evidence.

What do I need to provide for an effective UI critique?

For an effective UI critique, provide evidence intake such as screenshots, transcripts, traces, benchmarks, or artifacts. Supplying these materials allows the analysis to ground its evaluation criteria and corner-case coverage in real implementation data.