yolo-init

Stars9

Forks0

UpdatedJuly 7, 2026 at 06:40

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".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

CoriChui

CoriChui/yolo

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	yolo-init
description	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".

yolo-init

Make a repo YOLO-ready. Idempotent — safe to re-run (repair mode).

Resolve template sources via the plugin root. When YOLO is installed as a plugin (${CLAUDE_PLUGIN_ROOT} is set), read .claude/yolo/templates/* from ${CLAUDE_PLUGIN_ROOT}/.claude/yolo/templates/*; when the framework was copied into the project, read them project-relative (see conventions.md Where YOLO's files live). Either way, yolo-init writes only project state — workspace/, workspace/config.yaml, and the CLAUDE.md routing block. In plugin mode do not copy the framework (skills/conventions) into the project; it stays in the plugin and resolves via ${CLAUDE_PLUGIN_ROOT}.

Procedure

Create workspace/, workspace/features/, workspace/decisions/, workspace/debug/ if missing (each tracked; add a .gitkeep where empty). Ensure docs/ exists too — the single doc folder the docs engine indexes and where persisted intake lives; yolo keeps no workspace/intake/ shelf.
If workspace/config.yaml is missing, copy .claude/yolo/templates/config.yaml to it; set project.name to the repo directory name and project.base_branch via the detection rule in .claude/yolo/conventions.md (git symbolic-ref --short refs/remotes/origin/HEAD minus origin/, else first existing of main/master). If it exists, repair only: fill missing keys, never overwrite a user-set value.
Install the routing block: ensure the project CLAUDE.md contains the content of .claude/yolo/templates/claude-routing-block.md. If the /end markers already exist, replace the block between them; otherwise append it. (Idempotent.)
Commit (yolo: init).

Constraints

Never git-ignore workspace/ — it is the durable spine and must survive branches/worktrees.
Repair mode preserves existing config values; it only fills gaps.

More from this repository

same repository

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-decide

CoriChui/yolo

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".

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

name	yolo-init
description	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".

yolo-init

Make a repo YOLO-ready. Idempotent — safe to re-run (repair mode).

Procedure

Create workspace/, workspace/features/, workspace/decisions/, workspace/debug/ if missing (each tracked; add a .gitkeep where empty). Ensure docs/ exists too — the single doc folder the docs engine indexes and where persisted intake lives; yolo keeps no workspace/intake/ shelf.
If workspace/config.yaml is missing, copy .claude/yolo/templates/config.yaml to it; set project.name to the repo directory name and project.base_branch via the detection rule in .claude/yolo/conventions.md (git symbolic-ref --short refs/remotes/origin/HEAD minus origin/, else first existing of main/master). If it exists, repair only: fill missing keys, never overwrite a user-set value.
Install the routing block: ensure the project CLAUDE.md contains the content of .claude/yolo/templates/claude-routing-block.md. If the /end markers already exist, replace the block between them; otherwise append it. (Idempotent.)
Commit (yolo: init).

Constraints

Never git-ignore workspace/ — it is the durable spine and must survive branches/worktrees.
Repair mode preserves existing config values; it only fills gaps.