agentleFS
avelikiyavelikiy/great_cto/skills/decision-eval/SKILL.md

decision-eval

Skill112 starsChanged 2 months agoMITView on GitHub

Spawns the decision-scorer agent after architect proposes 2+ variants in an ADR. Produces a weighted scoring table and recommended choice saved to docs/decisions/.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    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:

    line 42
  2. Very specific:

    If VARIANT_COUNT >= 2, dispatch the agent:

    line 54
  3. Distinctive:

    After the agent completes, read the output file and surface the recommendation to the architect:

    line 70
  4. Distinctive:

    After scoring completes, architect may:

    line 99

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Decision Eval — automated scoring for architectural alternatives

Invoke after architect proposes 2+ variants, before creating gate:arch.

When to invoke

Invoke this skill when ALL of these are true:

  1. An ADR (docs/adr/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:**)
  2. The architect has not yet created gate:arch
  3. The user has not said "skip scoring", "no scoring", or "skip decision-eval"
  4. project_size in PROJECT.md is NOT nano

Skip silently (do not even mention) if any condition fails.

How to invoke

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/adr/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/.

Output location

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.

Skip conditions

Output nothing and proceed to the next step if:

  • project_size: nano in PROJECT.md
  • Fewer than 2 variants found in the ADR/ARCH doc
  • User message contains "skip scoring" or "skip decision-eval" or "no scoring"
  • The target document is a bug-fix or docs-only ADR (check title for "fix:", "docs:", "chore:")

Integration with architect workflow

This 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:

  • Accept the recommendation → proceed to gate:arch with the recommended option
  • Override the recommendation → document rationale in the ADR under a new ## Scoring Override section before creating gate:arch

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.