Yak pilot

The user asks for a result. You know the skills. Choose them, run them, and ask the user only where a human decision is necessary.

This skill plans and keeps the run on its plan. The phase skills do the work. unattended-run answers every question that is not a gate and keeps the decision log. customize-yak writes the profile.

1. Read the request, the state and the profile

1. Find the position with the state signals of ask-yak (references/process.md). If work for this slug has started, plan only the steps that are still to run.
2. Read the profile: the pilot: lines that check_yesyak.py prints. No pilot: line means no profile. Then the first message of the run asks the round of customize-yak ("Pilot profile") together with the blocking questions of section 2, and says that the run uses the default profile until the answer. customize-yak writes the answer.
3. Choose the route: a feature request goes to feature-delivery-pipeline, a bug report to bug-intake.
4. Read the code that the request touches, and give the "does it fit in one iteration?" verdict of the pipeline. A split is a gate: the user chooses the first delivery.

2. Ask only what blocks the run

A question blocks the run when both are true:

• The request, the code and the project docs do not answer it.
• A wrong guess changes a result that a user can see, or makes more than one step run again.