Flights#

A Flight is a supervised unit of work that can contain a plan, tasks and one or more isolated attempts. Attempts normally use Git worktrees so parallel agents do not edit the same checkout.

Before you start#

• The target project is a Git repository with a known base branch.
• Current local changes are committed or intentionally excluded.
• Every local or SSH target has a valid project path.
• You have defined a cost limit and permission posture appropriate to the task.

Plan and launch#

1. Open Flight Deck and create a Flight with a concrete outcome.
2. Start a planning conversation and refine the milestones.
3. Apply the plan only after reviewing task dependencies and file ownership.
4. Select one or more executors and confirm each base branch and target path.
5. Launch the attempts and watch the attention group for failures or approval requests.

PacketBench detects some path collisions, but task boundaries still need human review. Assign overlapping files to one attempt or sequence those tasks.

Review and integrate#

1. Open each completed attempt and inspect its commits and diff.
2. Run the project's relevant tests in the attempt worktree.
3. Accept or reject the result explicitly.
4. Integrate approved commits using the repository's normal merge process.
5. Clean up an attempt only after its useful commits are preserved.

Verify#

The Flight should show a terminal state for every attempt, the integration branch should contain only approved commits, and the primary checkout should be clean or contain only changes you recognise.

If it does not work#