yolo-intake

Étoiles9

Forks0

Mis à jour7 juillet 2026 à 06:10

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

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

description

yolo-intake

Intake is context enrichment, not fetching. yolo never fetches, imports, or copies external material. It simply references a selected folder — by default the project's docs/ — and reads from it to enrich a feature's context. Populating that folder (pulling in a Figma, a spec, a URL, a DB schema) is the job of the docs engine or another connector, done separately and outside yolo. yolo only reads what's already there.

The selected folder

The intake folder is intake.folder in workspace/config.yaml — default docs/. Point it at a different folder only if your reference material lives elsewhere.
Whatever is in that folder is YOLO's context shelf. YOLO reads it; it never puts things there.

Procedure

Resolve the intake folder from workspace/config.yaml (intake.folder, default docs/).
Read the relevant material from it for the feature — search the docs engine first, then read the specific files. Never fetch a live source. If needed context isn't in the folder, say so (a connector / docs-engine step must add it first) rather than fetching it yourself.
A feature brief points at the specific files it relies on via its intake_refs list — paths under the intake folder (e.g. docs/explanation/payments-spec.md).

Constraints

Never fetch or import. No WebFetch, no MCP fetch, no CLI pull, no copying into the workspace. Intake is strictly read-only over the selected folder.
One folder, one source of context — don't scatter reference material across the workspace.
If required context is missing from the folder, surface the gap; adding it is a connector / docs-engine concern, outside yolo.

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

description

yolo-intake

The selected folder

The intake folder is intake.folder in workspace/config.yaml — default docs/. Point it at a different folder only if your reference material lives elsewhere.
Whatever is in that folder is YOLO's context shelf. YOLO reads it; it never puts things there.

Procedure

Resolve the intake folder from workspace/config.yaml (intake.folder, default docs/).
Read the relevant material from it for the feature — search the docs engine first, then read the specific files. Never fetch a live source. If needed context isn't in the folder, say so (a connector / docs-engine step must add it first) rather than fetching it yourself.
A feature brief points at the specific files it relies on via its intake_refs list — paths under the intake folder (e.g. docs/explanation/payments-spec.md).

Constraints

Never fetch or import. No WebFetch, no MCP fetch, no CLI pull, no copying into the workspace. Intake is strictly read-only over the selected folder.
One folder, one source of context — don't scatter reference material across the workspace.
If required context is missing from the folder, surface the gap; adding it is a connector / docs-engine concern, outside yolo.