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/.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Invoke after architect proposes 2+ variants, before creating gate:arch.
Invoke this skill when ALL of these are true:
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:**)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/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/.
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:arch还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。
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).
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.
中文简介正在准备中。当前显示原文说明。