One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill yolo-project-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yolo-project
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/yolo-project
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill yolo-project-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a captain opens a session with a vague prompt like "let's work on the auth refresh", it is unclear which lifecycle skill should handle the request. This Skill acts as a top-level intent router that classifies the prompt, loads project context when needed, and chains to the correct lifecycle skill without guessing on ambiguous input. ## Core Features & Use Cases - Intent Classification: Maps prompt signals to one of six intents (resume, ad-hoc-code, research, plan, execute, archive) using an exhaustive routing table and disambiguation precedence rules. - Project Context Loading: Invokes /launch-project before project-bound skills like /create-spike, /create-plan, /execute-plan, and /archive-project, with bounded retry on refusal. - Ambiguity Handling: Refuses to auto-route unclear prompts and instead asks the captain a structured clarification listing candidate intents. - Use Case: A captain types "spec the channel registry" — the router classifies this as a plan intent, ensures /launch-project has loaded the project context, then invokes /create-plan with the original prompt verbatim. ## Quick Start Say "let's work on the auth refresh" or any topic-level request without a slash command, and the router will classify your intent and chain to the right lifecycle skill.

Frequently Asked Questions about yolo-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route an ambiguous prompt to the right lifecycle skill?▼

Invoke the router with a topic-level prompt like "let's work on X". It classifies the intent against an exhaustive signal table, loads project context if required, and invokes the matching lifecycle skill such as /create-spike or /create-plan.

What happens when a prompt matches multiple lifecycle intents?▼

Disambiguation precedence rules resolve conflicts: explicit slash commands win first, then session-opener phrasing, then explicit lifecycle phrasing, then plan/spike phrasing. Equal-strength signals with no rule trigger a clarification question instead of guessing.

Does the router override an explicit slash command?▼

No. If the captain explicitly types a command like /create-spike or /start-session, that call wins and the router is bypassed entirely. The router only handles prompts with no explicit skill invocation.

When does the router load project context before chaining?▼

Project context via /launch-project is loaded only for project-bound intents: research, plan, execute, and archive. Resume and ad-hoc code intents orient themselves and skip this step entirely.

What happens if the router cannot determine the target project?▼

It asks the captain for the project name once, retries /launch-project a single time with the response, and if that also fails it surfaces the refusal reason and stops. It never loops a third time or invents a project name.

When should I not use an intent router for lifecycle skills?▼

Do not route when the captain typed an explicit slash command, when already inside another skill that knows its target, or for pure Q&A with no work request. In those cases call the target skill directly or just answer.