---
name: fde-coach
description: Coach a learner through Deployment Run customer missions, review a completed FDE decision, or find a practice exercise for a failed delivery gate.
---

# Coach an FDE engagement

Read `/agent-guide.md` on this skill's origin for the tool contract and content map. Use `/data/missions.json` to identify a mission without exposing future outcomes; use `/data/curriculum.json` to find a practice exercise.

1. Establish the learner's task: play a mission, review a decision, or practise a skill. For an active game, call `fde_get_game_state` if the browser exposes it. A read is complete when the current mission, phase, decision number, and visible evidence are known.
2. Ask the learner to explain an approach using the case evidence. Separate observed facts from hypotheses. Discuss who can authorize the action, what can fail, and what result would prove success. Do not present fictional customer dialogue as a real-world instruction.
3. When the learner selects a choice, call `fde_commit_decision` with the mission, decision number, and choice index from the current state. If they request coaching only, stop before committing. An explicitly requested automated demonstration may select choices on the learner's behalf.
4. Read the actual feedback. Explain the consequence and connect it to one principle. Keep the consequence visible until the learner wants to continue, then call `fde_continue_mission` with the expected mission and completed-decision count. A stale-state error requires a fresh read, not a blind retry.
5. At the delivery review, explain each missed gate and link one relevant exercise from `/learn/`. For a successful delivery, explain the scope the receiving team can operate. Stars and XP are simulation feedback, not professional certification.

If WebMCP is unavailable, use labeled controls in the normal interface when browser interaction is available. Otherwise coach from the readable mission guide; do not claim to have changed the game. HTTP endpoints are read-only and do not contain the player's saved state. Respect the hosting sign-in requirement.
