Skip to content
cccskills
FreePublished on GitHub

decision-eval

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 English summary is being prepared. Showing the original description.

avelikiy/great_cto
See how to install

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

aesthetic-instrument

Free

great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 22, 2026

anti-patterns

Free

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 22, 2026

anydesign

Free

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 22, 2026

archetype-review-base

Free

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 22, 2026

brainstorming

Free

Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 22, 2026

codex-host

Free

Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 22, 2026

See all skills by avelikiy

Report a problem with this skill