# Thoroughness Scoring

Score every decision point with a Thoroughness Rating (1-10).

- Repository: https://github.com/rohitg00/pro-workflow (2940 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-09-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rohitg00/pro-workflow --skill thoroughness-scoring -g -a claude-code -y`
Codex: `npx skills add rohitg00/pro-workflow --skill thoroughness-scoring -g -a codex -y`
Cursor: `npx skills add rohitg00/pro-workflow --skill thoroughness-scoring -g -a cursor -y`
Gemini CLI: `npx skills add rohitg00/pro-workflow --skill thoroughness-scoring -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rohitg00/pro-workflow`

## Description

Score every decision point with a Thoroughness Rating (1-10). AI makes the marginal cost of doing things properly near-zero, pick the higher-rated option every time. Includes scope checks to distinguish contained vs unbounded work.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Thoroughness Scoring

AI drops the cost of doing things right to near-zero. Stop picking the quick hack when the thorough option takes the same wall-clock time with AI assistance.

## The Rating Scale

Every option gets a Thoroughness score (T:X/10):

| Score | What It Means |
|-------|---------------|
| T:10 | All edge cases handled, full test coverage, docs updated, error messages helpful |
| T:9 | Edge cases covered, tests pass, types solid, no shortcuts |
| T:8 | Happy path + error paths, good tests, clean types |
| T:7 | Happy path works, basic tests, no docs |
| T:5 | Works for the demo, fragile, manual testing only |
| T:3 | Quick hack, no tests, tech debt accruing |
| T:1 | Copy-paste from Stack Overflow, untested, hope it works |

## How to Present Options

When presenting choices, follow this format every time:

### 1. Re-State Context

The user may have been away. Start with orientation:

```text
PROJECT: my-app (branch: feat/rate-limiting)
TASK: Add rate limiting to the /api/upload endpoint
```

### 2. Rate Each Option

```text
Option A, Full rate limiter with sliding window (T:9/10)
  Manual estimate: 3-4 hours
  AI-assisted estimate: 15-20 minutes
  Covers: per-user limits, sliding window, Redis-backed, retry-after headers,
          429 responses, rate limit bypass for admin, tests for all paths

Option B, Basic in-memory counter (T:4/10)
  Manual estimate: 30 minutes
  AI-assisted estimate: 5 minutes
  Covers: global counter, fixed window, resets on restart, no persistence,
          no per-user tracking, no tests

Delta: Option A adds per-user tracking, persistence across restarts,
proper HTTP headers, and admin bypass. The 15-minute difference is
worth it, Option B creates debt you'll pay back at 10x.
```

### 3. Recommend

Always recommend the higher-thoroughness option. State the delta, what the user gains for the additional time.

The rest: https://github.com/rohitg00/pro-workflow/blob/HEAD/skills/thoroughness-scoring/SKILL.md