verdict

Compare technology options with weighted scoring and cited evidence.

8|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/duthaho/skillhub --skill verdict-duthaho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verdict
Source: https://github.com/duthaho/skillhub/tree/main/.claude/skills/verdict
Command: npx skills add https://github.com/duthaho/skillhub --skill verdict-duthaho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you make defensible technology decisions when you need to choose between tools, platforms, frameworks, or buy-vs-build options. It replaces guesswork and marketing noise with structured research, weighted scoring, and cited evidence.

Core Features & Use Cases

  • Decision Research: Compares 2–4 options across project health, community sentiment, technical fit, operations, and security.
  • Scorecard-Based Recommendation: Produces an ADR-style verdict with weighted criteria and an explicit recommendation for the stated context.
  • Revisit Support: Re-checks prior decisions against defined triggers so older recommendations can be validated or overturned when facts change.
  • Use Case: Ask whether to use PostgreSQL or MongoDB for a specific workload, or compare two frameworks before a team commits to one.

Quick Start

Ask the verdict skill to compare the options for your specific context, such as deciding between two databases for a new service.

Frequently Asked Questions about verdict

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

FAQPage Schema
How do I compare technology options for a specific architecture or product context?

To compare technology options for a specific architecture, you need an evidence-backed decision brief applying parallel research across project health, technical fit, and security. This yields an ADR-style verdict with weighted scoring, cited sources, and explicit assumptions to justify the final recommendation.

What is weighted scoring in technology selection and when do I need it?

Weighted scoring in technology selection evaluates multiple options against criteria like project health, community sentiment, and technical fit to produce a defensible ADR-style verdict. You need it when choosing frameworks or platforms to replace guesswork and marketing noise with cited evidence.

How do I write a decision brief for a buy-versus-build analysis?

Writing a decision brief for a buy-versus-build analysis requires comparing options across operations and security dimensions. It generates an ADR-style output with weighted criteria, cited sources, explicit dealbreakers, and a clear recommendation for your stated product context.

Can I re-check a prior technology recommendation when facts change?

Yes, you can re-check a prior technology recommendation by performing a revisit check against defined triggers. This validates or overturns older ADR-style decisions when project health, community sentiment, or technical fit facts change, ensuring your architecture choices remain defensible.

What are the limitations of using weighted scoring for framework comparison?

The limitation of weighted scoring for framework comparison is that it requires explicit assumptions and dealbreakers to be stated upfront. If your architecture context lacks defined triggers or clear criteria for project health and operations, the ADR-style verdict may not yield a defensible recommendation.