yolo-decide

Étoiles9

Forks0

Mis à jour7 juillet 2026 à 06:40

Use when facing a design or architecture decision that benefits from multiple perspectives before committing. Produces a decision record under workspace/decisions/. Triggers on "help me decide X vs Y", "which approach", "should we use A or B".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

CoriChui

CoriChui/yolo

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	yolo-decide
description	Use when facing a design or architecture decision that benefits from multiple perspectives before committing. Produces a decision record under workspace/decisions/. Triggers on "help me decide X vs Y", "which approach", "should we use A or B".

yolo-decide

Reach a defensible decision via multi-perspective analysis, and record it.

Procedure

The multi-perspective analysis runs at the billed agents.decide tier. Confirm the decision framing before launching it — the plan-gate analogue for a decision (.claude/yolo/conventions.md The two gates). STOP and wait for the human here (state the framing, then pause) — do not state the framing and slide into the analysis in the same turn. Skip only if the user pre-consented.
State the decision and the options crisply.
Argue each option from several lenses — at minimum correctness/risk, simplicity/maintainability, and pragmatism/cost. Surface the strongest case FOR and AGAINST each.
Recommend one option, with explicit rationale, the alternatives considered, dissents (minority concerns worth recording), and revisit triggers (conditions that should reopen this).
Write workspace/decisions/<slug>.md with: decision, rationale, approach, alternatives_considered, dissents, revisit_triggers, confidence. Confirm before overwriting an existing slug.
Commit (yolo: decision <slug>).

When to reach for `bakeoff` instead

yolo-decide is a single-pass, multi-lens analysis — right for most X-vs-Y calls. For a high-stakes, hard-to-reverse decision with several defensible options (architecture, migration, tool selection), the bakeoff skill runs a heavier judged tournament: it generates diverse candidate solutions, auto-derives a rubric for the problem, scores each with independent judges, and adversarially refutes the leader. If bakeoff is installed, offer it for those cases, then record its verdict as the decision here (workspace/decisions/<slug>.md) so the trail stays in one place.

Constraints

Read-only with respect to code; the only file you write is the decision record.
No status field; decisions are standalone records.
Run the multi-perspective analysis at the agents.decide tier from workspace/config.yaml.

Plus depuis ce dépôt

même dépôt

yolo-feature

CoriChui/yolo

Use when the user wants to build, add, or implement a feature. Captures intent, drafts a brief, confirms, then composes research → plan → execute → verify → finish. In a YOLO-initialized repo this takes precedence over generic brainstorming for feature intent.

2026-07-079

yolo-init

CoriChui/yolo

Use when setting up YOLO in a project for the first time, or repairing the setup. Scaffolds workspace/config.yaml and the features/, decisions/, and debug/ dirs (plus docs/ for the docs engine), and installs the CLAUDE.md routing block. Triggers on "set up YOLO here", "init yolo", "yolo init".

2026-07-079

yolo-intake

CoriChui/yolo

Use when a feature should draw on the project's reference material for context. yolo-intake does NOT fetch, import, or copy anything — it points YOLO at a selected folder (default `docs/`) and READS from it to enrich a feature's context. Getting material INTO that folder (a Figma, a spec, a URL, a schema) is the docs engine's or another connector's job, done separately. Triggers on "use the docs as context", "reference the spec/schema in docs", "the feature should read our docs".

2026-07-079

yolo-research

CoriChui/yolo

Use before planning a YOLO change, to understand the codebase and any cited intake before a plan is written. Read-only exploration that produces context for yolo-plan. Triggers on "understand how X works", "explore the code before we change it", or as the research step of yolo-feature.

2026-07-079

yolo-debug

CoriChui/yolo

Use when a reported problem, failure, or bug needs a systematic root-cause investigation — reproduce → isolate → fix → verify — recorded as one durable artifact. Triggers on "fix the 500 on login", "X is broken", "why is Y failing?", "debug this", "track down this bug".

2026-07-029

yolo-finish

CoriChui/yolo

Use when a feature is implemented and verified, to land it. Default path is PR + CI check, with the ship gate confirming before the irreversible merge; fast-local is the escape hatch. Includes the risk classifier whose hard triggers always stop for a human. Triggers on "ship it", "land this", "open a PR", or as the finish step of yolo-feature.

2026-07-029

yolo-decide

Reach a defensible decision via multi-perspective analysis, and record it.

Procedure

The multi-perspective analysis runs at the billed agents.decide tier. Confirm the decision framing before launching it — the plan-gate analogue for a decision (.claude/yolo/conventions.md The two gates). STOP and wait for the human here (state the framing, then pause) — do not state the framing and slide into the analysis in the same turn. Skip only if the user pre-consented.

State the decision and the options crisply.

Argue each option from several lenses — at minimum correctness/risk, simplicity/maintainability, and pragmatism/cost. Surface the strongest case FOR and AGAINST each.

Recommend one option, with explicit rationale, the alternatives considered, dissents (minority concerns worth recording), and revisit triggers (conditions that should reopen this).

Write workspace/decisions/<slug>.md with: decision, rationale, approach, alternatives_considered, dissents, revisit_triggers, confidence. Confirm before overwriting an existing slug.

Commit (yolo: decision <slug>).

When to reach for bakeoff instead

Constraints

Read-only with respect to code; the only file you write is the decision record.

No status field; decisions are standalone records.

Run the multi-perspective analysis at the agents.decide tier from workspace/config.yaml.

yolo-decide

yolo-decide

Procedure

When to reach for bakeoff instead

Constraints

Plus depuis ce dépôt

Plus depuis ce dépôt

yolo-decide

Procedure

When to reach for bakeoff instead

Constraints

When to reach for `bakeoff` instead

When to reach for `bakeoff` instead