Skill
yolo-debug
Use when a reported problem, failure, or bug needs a systematic root-cause investigation — reproduce → isolate → fix → verify — recorded as one durable…
Development
Skill
/yolo-roadmap
Use when the user has a large or fuzzy goal that should be decomposed into several features. Produces N feature briefs (optionally sharing a milestone label) — a one-time act that returns briefs, not a container. Triggers on "break this epic into features", "plan a milestone",
Install
$ npx -y skills add CoriChui/yolo --skill yolo-roadmap --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/yolo-roadmap
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user has a large or fuzzy goal that should be decomposed into several features. Produces N feature briefs (optionally sharing a milestone label) — a one-time act that returns briefs, not a container. Triggers on "break this epic into features", "plan a milestone",
SKILL.md
yolo-roadmap.SKILL.mdname: yolo-roadmap
description: Use when the user has a large or fuzzy goal that should be decomposed into several features. Produces N feature briefs (optionally sharing a milestone label) — a one-time act that returns briefs, not a container. Triggers on "break this epic into features", "plan a milestone", "decompose this".
yolo-roadmap
Turn one big goal into several atomic feature briefs. There is no "release" container — just briefs, optionally tagged with a shared `milestone`.
Procedure
1. Clarify the big goal and its boundary (what's out of scope). Optionally invoke yolo-research for codebase context. 2. Decompose into independent features, each shippable on its own. Note any cross-feature `depends_on` (honored by the model; there is no DAG machine). 3. For each feature, draft `workspace/features/<slug>/brief.md` from `.claude/yolo/templates/brief.md` — set `goal`, `success_criteria`, and a shared `milestone:` value if they ship as a set. 4. Present the proposed feature list for approval BEFORE creating the briefs — the plan-gate analogue for a roadmap; no billed code work happens here (`.claude/yolo/conventions.md` *The two gates*). Skip only if the user pre-consented. 5. On approval, write and commit each brief (`yolo: brief <slug>`). Each is later picked up by yolo-feature.
Constraints
- You only create briefs (status "planned"). You do not branch, plan, or execute — that is yolo-feature, per feature.
- No container, no lifecycle, no status field. Grouping is the `milestone:` label only.
- Run decomposition/analysis at the `agents.roadmap` tier from `workspace/config.yaml`.
Read more
name: yolo-roadmap description: Use when the user has a large or fuzzy goal that should be decomposed into several features. Produces N feature briefs (optionally sharing a milestone label) — a one-time act that returns briefs, not a container. Triggers on "break this epic into features", "plan a milestone", "decompose this".
yolo-roadmap
Turn one big goal into several atomic feature briefs. There is no "release" container — just briefs, optionally tagged with a shared `milestone`.
Procedure
1. Clarify the big goal and its boundary (what's out of scope). Optionally invoke yolo-research for codebase context. 2. Decompose into independent features, each shippable on its own. Note any cross-feature `depends_on` (honored by the model; there is no DAG machine). 3. For each feature, draft `workspace/features/<slug>/brief.md` from `.claude/yolo/templates/brief.md` — set `goal`, `success_criteria`, and a shared `milestone:` value if they ship as a set. 4. Present the proposed feature list for approval BEFORE creating the briefs — the plan-gate analogue for a roadmap; no billed code work happens here (`.claude/yolo/conventions.md` *The two gates*). Skip only if the user pre-consented. 5. On approval, write and commit each brief (`yolo: brief <slug>`). Each is later picked up by yolo-feature.
Constraints
- You only create briefs (status "planned"). You do not branch, plan, or execute — that is yolo-feature, per feature.
- No container, no lifecycle, no status field. Grouping is the `milestone:` label only.
- Run decomposition/analysis at the `agents.roadmap` tier from `workspace/config.yaml`.
Ships withyolo
Reasoning-first development for Claude Code. Git is the source of truth; status is derived, never stored. YOLO turns "I want X" into a planned, executed, verified, and landed change, driven by conversation and git rather than tracked status files.
Get the whole plugin
Other skills on yolo.
Skill
yolo-decide
Use when facing a design or architecture decision that benefits from multiple perspectives before committing. Produces a decision record under…
Skill
yolo-feature
Use when the user wants to build, add, or implement a feature. Captures intent, drafts a brief, confirms, then composes research → plan → execute → verify →…
Skill
yolo-finish
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;…
Skill
yolo-init
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/…
Skill
yolo-intake
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…