prepare

Writes a rover loop file into another repository's .autonomous directory for later wake-up.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill prepare-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/rover/skills/prepare
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill prepare-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the conversation context for an autonomous mission lives in one repo but the work must happen in another, this Skill captures the mission now and leaves a dormant loop file in the target repo so the operator can start it later from inside that repo. ## Core Features & Use Cases - Deferred mission setup: Writes a fully contextualized rover loop file (<repo>/.autonomous/<NAME>.md) with dispatch, context, and log entries, without starting any continuation or creating branches. - Path resolution and validation: Resolves absolute, tilde, or relative target repo paths, verifies .git/ exists, and halts only when no explicit path is given. - Naming and collision handling: Distils ALL-CAPS goal-oriented loop file names and kebab-case branch suggestions, appending numeric suffixes instead of overwriting existing missions. - Use Case: While discussing an OAuth fix in your current session, run /rover:prepare ~/code/foo fix the OAuth flow to queue the mission in the foo repo, then later cd there, create the branch, and wake it with /rover:rover. ## Quick Start Ask the agent to prepare a rover mission in another repository by giving the target repo path and the mission, for example: prepare a rover loop in ~/code/foo to fix the OAuth flow.

Frequently Asked Questions about prepare

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

FAQPage Schema
How do I queue an autonomous rover mission in another repository?▼

Invoke /rover:prepare with the target repo path and a mission description, such as /rover:prepare ~/code/foo fix the OAuth flow. It writes a loop file into that repo's .autonomous directory, which you later wake with /rover:rover from inside that repo.

What is the difference between rover prepare and rover dispatch?▼

Prepare writes the loop file and .gitignore only, leaving the mission dormant with no continuation, branch, or first SURVEY iteration. Rover dispatch runs the full setup immediately in the current working directory and starts the phase machine right away.

Can I use an owner/repo slug instead of a path with prepare?▼

No, prepare only accepts explicit paths: absolute, tilde-expanded, or relative paths containing a slash. A bare name or owner/repo slug causes it to ask for an explicit path, since it has no clone-layout mapping to fall back on.

What happens if a loop file with the same name already exists?▼

Prepare never overwrites an existing loop file in the target's .autonomous directory. It appends a numeric suffix like ADD-RAW-SOURCES-SUPPORT-2.md and tells the operator, preserving any in-flight or queued mission.

Does prepare create the git branch or commit anything in the target repo?▼

No, prepare only writes the loop file and a .gitignore containing an asterisk. The operator creates the suggested kebab-case branch with git checkout -b at wake time, and nothing is committed, pushed, or merged.