Rework

Author: olivomarco

modules/_TEMPLATE/challenge/README.md

@@ -35,7 +35,7 @@ REPLACE: Continue with numbered steps.
 
 REPLACE: Keep steps granular — one action per step where possible.
 
-## Delivery evidence and handover
+## Implementation record and handover
 
 - [ ] First observable implementation or governance outcome
 - [ ] Second observable evidence or operational artefact

modules/ghaw/challenges/00-setup/COACH.md

@@ -11,7 +11,7 @@
 ## Facilitation Hints
 
 - **Push Codespaces first.** If local setup consumes more than 10 minutes, redirect to Codespaces.
-- Ask for a show-of-hands "green terminal" check after the first 10 minutes.
+- Ask for a show-of-hands working-terminal check after the first 10 minutes.
 - Pair any participant who is blocked with a working neighbor; don't let one blocker stall the group.
 - `gh aw` installs automatically via `postCreate.sh` in both Codespaces and local dev containers. If a participant sees "command not found", the postCreate script likely failed — have them rebuild the container.
 - If `gh aw trial ... --dry-run` fails with an API key error, GitHub Copilot is the default zero-config engine. Confirm the participant's account has an active Copilot subscription. For Claude/OpenAI/Gemini, point them to `github.com/settings/codespaces` to add secrets.

modules/ghaw/challenges/01-morning-briefing/COACH.md

@@ -2,11 +2,11 @@
 
 ---
 
-## Grounding conversation (you will be called)
+## Facilitated application
 
-**Required coach check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
+**Required facilitator check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
 
-**Their question:** Coach conversation — what daily status update do you or your team assemble by hand today that this scheduled briefing pattern could replace, and what would you trust it to send unsupervised? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+**Discuss:** What daily status update do you or your team assemble by hand today that this scheduled briefing pattern could replace, and what would you trust it to send unsupervised? Connect it to a project, task, or workflow you own.
 
 Use these follow-ups to steer the conversation:
 - Ask them to name the exact repo, project, or team channel where a status update is assembled by hand today.

modules/ghaw/challenges/01-morning-briefing/README.md

@@ -49,7 +49,7 @@ By the end of this activity, your squad will:
 - [ ] `.github/workflows/morning-briefing.lock.yml` is generated after compiling
 - [ ] At least one issue was created when the workflow ran (or manual trigger via `workflow_dispatch`)
 - [ ] Issue body includes a summary of recent activity (issues opened, PRs, etc.)
-- [ ] Coach conversation — what daily status update do you or your team assemble by hand today that this scheduled briefing pattern could replace, and what would you trust it to send unsupervised? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+- [ ] Discuss what daily status update you or your team assemble by hand today that this scheduled briefing pattern could replace, and what you would trust it to send unsupervised. Connect it to a project, task, or workflow you own.
 
 ---
 

modules/ghaw/challenges/03-the-watcher/COACH.md

@@ -2,11 +2,11 @@
 
 ---
 
-## Grounding conversation (you will be called)
+## Facilitated application
 
-**Required coach check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
+**Required facilitator check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
 
-**Their question:** Coach conversation — which repository events do you currently notice only after the fact, and what would change if a push-triggered agent flagged risky file changes the moment they land? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+**Discuss:** Which repository events do you currently notice only after the fact, and what would change if a push-triggered agent flagged risky file changes the moment they land? Connect it to a project, task, or workflow you own.
 
 Use these follow-ups to steer the conversation:
 - Ask them to name a directory or file in their own repo whose changes carry outsized risk.

modules/ghaw/challenges/03-the-watcher/README.md

@@ -49,7 +49,7 @@ By the end of this activity, your squad will:
 - [ ] When you push changes to the watched directory, the workflow runs
 - [ ] A comment appears on the commit summarizing the changes (e.g., "Modified 3 files in docs/")
 - [ ] Logs show the agent detected which files were changed
-- [ ] Coach conversation — which repository events do you currently notice only after the fact, and what would change if a push-triggered agent flagged risky file changes the moment they land? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+- [ ] Discuss which repository events you currently notice only after the fact, and what would change if a push-triggered agent flagged risky file changes the moment they land. Connect it to a project, task, or workflow you own.
 
 ---
 

modules/ghaw/challenges/06-review-buddy/COACH.md

@@ -2,11 +2,11 @@
 
 ---
 
-## Grounding conversation (you will be called)
+## Facilitated application
 
-**Required coach check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
+**Required facilitator check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
 
-**Their question:** Coach conversation — which parts of your code review are mechanical enough to delegate to a first-pass bot, and which judgment calls must always stay with a human reviewer? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+**Discuss:** Which parts of your code review are mechanical enough to delegate to a first-pass bot, and which judgment calls must always stay with a human reviewer? Connect it to a project, task, or workflow you own.
 
 Use these follow-ups to steer the conversation:
 - Ask them to name a repo where a first-pass review bot would reduce reviewer load.

modules/ghaw/challenges/06-review-buddy/README.md

@@ -73,7 +73,7 @@ Create a gh-aw workflow named `review-buddy.md` in `.github/workflows/` that:
   - 2+ observations
   - An encouraging sign-off
 - [ ] The comment feels useful (not spam)
-- [ ] Coach conversation — which parts of your code review are mechanical enough to delegate to a first-pass bot, and which judgment calls must always stay with a human reviewer? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+- [ ] Discuss which parts of your code review are mechanical enough to delegate to a first-pass bot, and which judgment calls must always stay with a human reviewer. Connect it to a project, task, or workflow you own.
 
 ---
 

modules/ghaw/challenges/07-slash-and-burn/COACH.md

@@ -2,11 +2,11 @@
 
 ---
 
-## Grounding conversation (you will be called)
+## Facilitated application
 
-**Required coach check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
+**Required facilitator check-in:** before completion, ask the customer practitioner to connect the exercise to work they actually own.
 
-**Their question:** Coach conversation — what context do you and your teammates rebuild by hand by scrolling long threads, and which on-demand slash command would you actually reach for in your daily work? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+**Discuss:** What context do you and your teammates rebuild by hand by scrolling long threads, and which on-demand slash command would you actually reach for in your daily work? Connect it to a project, task, or workflow you own.
 
 Use these follow-ups to steer the conversation:
 - Ask where they and teammates repeatedly rebuild context by scrolling long threads.

modules/ghaw/challenges/07-slash-and-burn/README.md

@@ -77,7 +77,7 @@ Create a gh-aw workflow named `slash-commands.md` in `.github/workflows/` that:
   - At least 2 key points from the discussion
   - Next steps or recommendation
 - [ ] Only authorized users (repo members) can trigger the command
-- [ ] Coach conversation — what context do you and your teammates rebuild by hand by scrolling long threads, and which on-demand slash command would you actually reach for in your daily work? Talk it through with your coach and connect it to a real project, task, or workflow you own.
+- [ ] Discuss what context you and your teammates rebuild by hand by scrolling long threads, and which on-demand slash command you would actually reach for in your daily work. Connect it to a project, task, or workflow you own.
 
 ---