From great_cto
Spawns decision-scorer agent to weigh architectural alternatives from ADR or ARCH doc against project criteria, producing a scored recommendation table saved to docs/decisions/.
How this skill is triggered — by the user, by Claude, or both
Slash command
/great_cto:decision-evalWhen to use
Apply when: - architect has written an ADR with 2+ alternatives under ## Alternatives Considered or ## Options - architect is about to finalize a multi-variant decision and needs an objective tie-breaker - CTO explicitly requests scoring before gate:arch approval Do NOT apply when: - The change is a bug fix, docs-only, or style/formatting update - The ADR has only 1 option (no real alternatives) - User says "skip scoring" or "no scoring" - project_size is nano (overhead exceeds value)
docs/decisions/**docs/architecture/**.great_cto/PROJECT.mdThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Invoke after architect proposes 2+ variants, before creating gate:arch.
Invoke after architect proposes 2+ variants, before creating gate:arch.
Invoke this skill when ALL of these are true:
docs/decisions/ADR-*.md) or ARCH doc (docs/architecture/ARCH-*.md)
contains a section with 2 or more named alternatives (look for
## Alternatives Considered, ## Options, or bold-prefixed options like
**Option A:**)gate:archproject_size in PROJECT.md is NOT nanoSkip silently (do not even mention) if any condition fails.
Read the most recent ADR or ARCH doc to confirm 2+ variants exist, then spawn
the decision-scorer agent with the file path as context:
# Identify target document
TARGET=$(ls -t docs/decisions/ADR-*.md 2>/dev/null | head -1)
[ -z "$TARGET" ] && TARGET=$(ls -t docs/architecture/ARCH-*.md 2>/dev/null | head -1)
# Confirm 2+ variants
VARIANT_COUNT=$(grep -cE "^\*\*[A-Za-z]|^### [A-Za-z]|^- \*\*[A-Za-z]" "$TARGET" 2>/dev/null || echo 0)
If VARIANT_COUNT >= 2, dispatch the agent:
Agent: decision-scorer
Context: <TARGET file path>
Task: Score the architectural variants in <TARGET> against .great_cto/PROJECT.md criteria.
Save output to docs/decisions/.
The decision-scorer agent saves results to:
docs/decisions/DECISION-<slug>-<YYYYMMDD>.md
After the agent completes, read the output file and surface the recommendation to the architect:
Decision scoring complete:
Recommended: <variant name> (<score>/5.00)
Runner-up: <variant name> (<score>/5.00)
Full report: docs/decisions/DECISION-<slug>-<YYYYMMDD>.md
Architect: review the scoring rationale before accepting or overriding the recommendation.
Output nothing and proceed to the next step if:
project_size: nano in PROJECT.mdThis skill sits between Step 4 (Write ADR) and Step 5 (Create gate:arch) in
agents/architect.md. Architect invokes it by name:
Invoke skill: decision-eval
After scoring completes, architect may:
## Scoring Override section before creating gate:archnpx claudepluginhub avelikiy/great_ctoEvaluates architectural decisions and produce ADRs following the project template. Use when making architectural decisions, evaluating trade-offs, or creating ADRs.
Builds weighted decision matrices, analyzes trade-offs, and generates ADRs for architectural, technical, and process decisions like database selection or framework choice.
Evaluates technology alternatives against criteria like fit, complexity, team familiarity, scalability, and security; scores options and documents ADRs.