goal-flight git:20260902.669456fA

Immutable. This exact content is served forever at /api/v1/blob/62db560f288d813b.

---
name: goal-flight
description: "Use when the user invokes /goal-flight or asks for Goal Flight to plan, dispatch, review, recover, or resume a long-running orchestrated repository run from file-backed state."
---

# goal-flight

Use this skill when a repository task needs durable planning, resumable work,
worker dispatch, review flights, or handoff notes that survive context loss.

## Load Order

1. Read the repository `AGENTS.md` first when present.
2. Read the repository root `SKILL.md` as the canonical Goal Flight workflow.
3. Read `protocols/guidance-extended.md` by default — non-frontier controllers
   benefit from its worked examples and expanded rationale for the core's rules;
   skip only when context is tight (the core alone is complete).
4. Read the newest relevant `docs-private/RESUME-NOTES-*.md` only when the task
   asks to resume prior Goal Flight work.

## Operating Rules

- Treat repository Markdown plus Git as canonical state.
- Keep queue, ledger, status, review, and handoff artifacts file-backed.
- Treat OpenCode session state, chat, and host config as advisory.
- For significant coding, decompose the task before implementation.
- For review flights, write prompts and outputs to files, then summarize only
  decisions and findings into the live conversation.
- Do not rewrite the root `SKILL.md` during setup. Setup registers checked-in
  wrappers and config only.

## Skill root

Live controllers load the installed skill pin at `$GOALFLIGHT_ROOT` or
`~/.goal-flight/skill/`, not a live source checkout. Run every
`python3 <skill-root>/scripts/...` command from that pin
(`$GOALFLIGHT_ROOT/scripts` or `~/.goal-flight/skill/scripts`). When
working inside the goal-flight repository itself, `<skill-root>` is the
repository root. The project tree is `$GOALFLIGHT_PROJECT_ROOT`, a named
checkout, or the live controller project — pass `--project-root` when the
cwd is not that tree. Doctor warns when this installed OpenCode wrapper has
drifted from the repo copy; resync with `./install.sh opencode`.

## Setup

Use setup for host registration and machine bootstrap. Use init for
project-local state and execution readiness.

From the cloned Goal Flight repository, run:

```shell
./setup.sh --opencode
./setup.sh --apply --yes --opencode

# Optional project-local install for one repository:
./setup.sh --apply --yes --opencode-project /path/to/project
```

Dry-run output must show every planned copy, merge, link, or registration
before mutation. Apply requires explicit approval and writes a machine-local
backup manifest for rollback.

OpenCode setup installs global agent instructions, this personal skill, and a
context-mode MCP entry in `opencode.json`. Project-local setup writes the same
wrapper under `.opencode/` in the target repository and merges project
`AGENTS.md` when selected. Use `--opencode-agents-standard` for the shared
`~/.agents/skills/` location, or `--opencode-link-claude` to symlink OpenCode's
skill directory to an existing Claude skill checkout. After setup, verify MCP
discovery with `opencode mcp list` and `opencode mcp auth list` when OAuth
servers need attention.

After setup, run Goal Flight init in the target project. Init runs doctor,
capacity checks, worker readiness checks, and writes compact project-local
caveats.