菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
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".
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".
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.
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".
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.
| 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". |
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}.
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.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.CLAUDE.md contains the content of .claude/yolo/templates/claude-routing-block.md. If the <!-- YOLO:routing-block start -->/end markers already exist, replace the block between them; otherwise append it. (Idempotent.)yolo: init).workspace/ — it is the durable spine and must survive branches/worktrees.