bakeoff
Runs a judged tournament between candidate solutions to one decision, scoring them against each other so you can see which option holds up. A Claude Code skill.
1 skill2 agents10
@corichuiDevelopment
Plugin
yolo
Turns a request like I want X into a planned, built, checked, and merged change, guided by conversation and git instead of status files you must keep current. Covers debugging, design decisions, and feature delivery.
Plugin Signal69/100Solid
maintained99
capable37
documented100
adopted21
Claude Code
> /plugin marketplace add CoriChui/yolo> /plugin install yolo@yolo
Codex
$ npx skills add CoriChui/yolo -a codex
Cursor
$ npx skills add CoriChui/yolo -a cursor
Gemini CLI
$ npx skills add CoriChui/yolo -a gemini-cli
GitHub Copilot
$ copilot plugin marketplace add CoriChui/yolo$ copilot plugin install yolo@yolo
OpenCode
$ npx skills add CoriChui/yolo -a opencode
Windsurf
$ npx skills add CoriChui/yolo -a windsurf
What's inside
5 Skills
/yolo-briefUse to record a new feature in a YOLO repo, or to cancel one. Writes workspace/features/<slug>/brief.md with a goal and checkable success criteria, taken from an approved design spec when one exists. Triggers on "track this as a feature", "write a brief for X", "track it from/yolo-initUse when setting up YOLO in a repo for the first time, or repairing the setup. Creates workspace/features/ and workspace/config.yaml. Triggers on "set up YOLO here", "init yolo", "yolo init"./yolo-nextUse when the user asks what to work on next, what to pick up, or what to prioritize in a YOLO repo. Ranks the backlog from derived status, dependencies, stalled work, open issues and code TODOs, and recommends the top 3 with reasons. Read-only. Triggers on "what next", "what/yolo-statusUse when the user asks where things stand, what's in progress, what's landed, or "where was I" in a YOLO repo. Derives every feature's status from git and the briefs; nothing is read from a stored status field./yolo-verifyUse to check a feature branch against its brief's success_criteria and record the result. Writes verification.md and, on a full pass, commits it with the YOLO-Verified trailer. Triggers on "verify this feature", "does it meet the criteria", "yolo verify".
README
YOLO
A thin state layer for agent-driven feature work. A feature is a short brief plus a git branch, and its status is derived from git every time you ask. Nothing is stored, so nothing drifts.
YOLO doesn't tell your agent how to plan, build or review. Use whatever you already use for that (plan mode, subagents, code review, your own habits). YOLO only answers two questions reliably: what are we building, and where does each thing stand.
How it works
workspace/features/<slug>/brief.mdholds the goal and checkable success criteria.feature/<slug>is the branch the work happens on.yolo-verifychecks the branch against the criteria and commits the evidence with aYOLO-Verified: truetrailer.- Merging the branch is what lands it. Plain merges, GitHub PR merges and GitLab merges are all detected from history, with or without the branch deleted.
Status, first match wins:
| Status | Meaning |
|---|---|
| landed | the branch was merged into base |
| verified | the branch tip passed yolo-verify and hasn't been merged yet |
| in-progress | the branch exists |
| planned | there's a brief but no branch yet |
| cancelled | the brief has cancelled: true |
Squash and fast-forward merges don't leave a merge commit naming the branch. If you merge
that way, put YOLO-Feature: <slug> as the last paragraph of the commit message.
The exact rules are in conventions.md.
Skills
| Skill | Use it to |
|---|---|
yolo-brief | record a feature (goal + success criteria), or cancel one |
yolo-status | see where every feature stands |
yolo-next | get the top 3 things to work on next, with reasons |
yolo-verify | check a branch against its brief and record the result |
yolo-init | set up workspace/ in a repo |
Install
/plugin marketplace add CoriChui/yolo
/plugin install yolo@yolo
Then say "set up YOLO here" in the repo.
A feature, start to finish
you: (optional) design it first; save the approved spec as
workspace/features/csv-export/spec.md
you: track CSV export for the reports page as a feature
yolo: writes brief.md, criteria taken from the spec -> planned
prints the branch command and a ready /goal line
you: git switch -c feature/csv-export main -> in-progress
...plan and build however you like, or paste the /goal line
so the session keeps working until verification passes...
you: verify csv-export
yolo: runs tests, checks each criterion, commits evidence -> verified
you: merge the PR -> landed
A brief's refs field links its spec, plan or ticket. Keeping spec.md and plan.md
next to the brief keeps a feature's files together; YOLO itself only reads the brief.
Upgrading from 0.4
0.5 drops the workflow: the feature/plan/research/finish skills, the two gates, task
trailers, decisions, debug records, intake and the routing block. Old repos keep working.
yolo/done/<slug> tags and YOLO-Feature trailers still count as landed, and leftover
plan.md, research.md and YOLO-Task trailers are simply ignored.
Tests
bash docs/validation/git-acceptance/run.sh
Builds throwaway repos and checks every status rule against real git, including the edge cases that broke earlier versions.
License
MIT
Stars on GitHub
Momentum
- stars in total
- 9
File tree
More plugins by @corichui.
View @corichui’s profile@corichuiSimilar plugins.
superpowers
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
15 skills1 hook311k
@obraskills
Helps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
31 skills309k
@mattpocockecc
Gives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
200 skills71 agents1 MCP+3+2+2+2+2+2+2+1+1302k
@affaan-mreact
Developer tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
14 skills4 agents252k
@facebookQuestions about yolo.
Turns a request like I want X into a planned, built, checked, and merged change, guided by conversation and git instead of status files you must keep current. Covers debugging, design decisions, and feature delivery. Install it with the command on its page. It includes yolo-brief, yolo-init, yolo-next. Its skills do not fire on their own yet. Free and open source.
- What is yolo?
- Turns a request like I want X into a planned, built, checked, and merged change, guided by conversation and git instead of status files you must keep current. Covers debugging, design decisions, and feature delivery.
- How do I install yolo?
- Run these in Claude Code: /plugin marketplace add CoriChui/yolo then /plugin install yolo@yolo. Then prompt normally.
- Does yolo auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin.
- Is yolo free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.
- Which coding agents can use yolo's skills?
- yolo installs in Claude Code, and its skills also install in Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI. Each skill's page has the install command. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it