name: yolo
description: "Use when the user says 'yolo' to delegate autonomous completion, such as 'ok now yolo it'; not when merely quoting or discussing the phrase."
YOLO
Treat activation as “go” for the established job, not merely the next step.
Reconstruct scope, acceptance criteria, constraints, and preferences from available context.
Own completion end to end: implement, integrate, verify, review, fix findings, clean up task-created scratch artifacts, deliver.
Aim for finished, dependable results; do not stop at scaffolding, partial implementation, or an unexecuted plan.
Infer decisions from user instructions, prior discussion, approved artifacts, project conventions, and existing behavior, in that order.
Resolve remaining ambiguity with the smallest safe, reversible choice that satisfies the goal.
Investigate uncertainty using available tools and evidence before asking the user.
Continue through recoverable failures; diagnose, fix, retry, or choose a valid alternative within applicable workflow limits.
Do not interrupt for routine decisions, reassurance, milestone approval, or permission already granted.
Load applicable task-specific skills; preserve their authorization rules, required confirmations, gates, stop conditions, and retry limits.
Honor authorization already granted by the encompassing request; do not ask again unless an applicable rule requires confirmation.
Commits and delivery
Activation authorizes small, coherent, task-scoped commits as useful recovery checkpoints; follow applicable Git skills and repository checks.
Inspect the owning repository's instructions, branches, tracking configuration, and recent history before choosing a delivery workflow.
Follow established repository workflow, not a generic branch/PR default.
Activation authorizes ordinary pushes to the established destination, including trunk when direct-to-trunk is the repository workflow.
Create a feature branch or PR only when repository rules or observed workflow call for one; reuse existing task branches and PRs.
Explicit user direction overrides inferred conventions; branch protection and required approvals remain binding.
Do not publish when destination or visibility is genuinely ambiguous.
This authorization excludes merging, releases, deployment, force-pushes, and bypassing required confirmations or protections.
Write commit messages, PR titles, descriptions, and comments in the user's established voice; load speak-as-oliver for outward-facing text.
Follow repository rules and templates for message format, identifiers, changelogs, and release notes.
Repository requirements take precedence over stylistic preferences.
Boundaries and completion
Preserve established scope, unrelated work, safety constraints, and permission boundaries.
Do not interpret autonomy as authorization to spend money, expose secrets, perform destructive actions, or publish beyond the bounded Git/PR authorization above.
Stop only for a true hard blocker: missing essential access or input, irreconcilable requirements, a consequential action requiring approval not already granted, or a mandatory workflow stop.
Scope each blocker to affected tasks; an unmet delivery gate does not block independent implementation.
Finish independent authorized work first; ask only for the specific missing decision, input, or authorization.
Verify observable outcomes against acceptance criteria; never substitute confidence for evidence or claim unverified perfection.
Finish with concise results, verification evidence, and any unresolved limitations.
---
name: yolo
description: "Use when the user says 'yolo' to delegate autonomous completion, such as 'ok now yolo it'; not when merely quoting or discussing the phrase."
---
# YOLO
- Treat activation as “go” for the established job, not merely the next step.
- Reconstruct scope, acceptance criteria, constraints, and preferences from available context.
- Own completion end to end: implement, integrate, verify, review, fix findings, clean up task-created scratch artifacts, deliver.
- Aim for finished, dependable results; do not stop at scaffolding, partial implementation, or an unexecuted plan.
- Infer decisions from user instructions, prior discussion, approved artifacts, project conventions, and existing behavior, in that order.
- Resolve remaining ambiguity with the smallest safe, reversible choice that satisfies the goal.
- Investigate uncertainty using available tools and evidence before asking the user.
- Continue through recoverable failures; diagnose, fix, retry, or choose a valid alternative within applicable workflow limits.
- Do not interrupt for routine decisions, reassurance, milestone approval, or permission already granted.
- Load applicable task-specific skills; preserve their authorization rules, required confirmations, gates, stop conditions, and retry limits.
- Honor authorization already granted by the encompassing request; do not ask again unless an applicable rule requires confirmation.
## Commits and delivery
- Activation authorizes small, coherent, task-scoped commits as useful recovery checkpoints; follow applicable Git skills and repository checks.
- Inspect the owning repository's instructions, branches, tracking configuration, and recent history before choosing a delivery workflow.
- Follow established repository workflow, not a generic branch/PR default.
- Activation authorizes ordinary pushes to the established destination, including trunk when direct-to-trunk is the repository workflow.
- Create a feature branch or PR only when repository rules or observed workflow call for one; reuse existing task branches and PRs.
- Explicit user direction overrides inferred conventions; branch protection and required approvals remain binding.
- Do not publish when destination or visibility is genuinely ambiguous.
- This authorization excludes merging, releases, deployment, force-pushes, and bypassing required confirmations or protections.
- Write commit messages, PR titles, descriptions, and comments in the user's established voice; load speak-as-oliver for outward-facing text.
- Follow repository rules and templates for message format, identifiers, changelogs, and release notes.
- Repository requirements take precedence over stylistic preferences.
## Boundaries and completion
- Preserve established scope, unrelated work, safety constraints, and permission boundaries.
- Do not interpret autonomy as authorization to spend money, expose secrets, perform destructive actions, or publish beyond the bounded Git/PR authorization above.
- Stop only for a true hard blocker: missing essential access or input, irreconcilable requirements, a consequential action requiring approval not already granted, or a mandatory workflow stop.
- Scope each blocker to affected tasks; an unmet delivery gate does not block independent implementation.
Finish independent authorized work first; ask only for the specific missing decision, input, or authorization.
- Verify observable outcomes against acceptance criteria; never substitute confidence for evidence or claim unverified perfection.
- Finish with concise results, verification evidence, and any unresolved limitations.