Problem statement
Step 7 (07-your-first-workflow.md) tells learners to "run this prompt" in your AI agent without naming a specific surface (Copilot CLI vs. VS Code Copilot Chat vs. the Agents-tab prompt box). The Monte Carlo simulation shows this step is now the top dropout driver (23.5% conditional dropout among 22,269 at-risk runs), split between copilot-access-missing (3,762 failures) and workflow-authoring-friction (1,471 failures). tool: CCA learners are disproportionately affected because they must independently translate the generic phrase into the Agents-tab flow.
Proposed change
Add one short, explicit branch immediately before the authoring prompt block that names the exact surface per tool preference (Copilot CLI command, VS Code Copilot Chat panel, or GitHub Agents tab), mirroring the pattern already used correctly in the earlier "Verify Copilot access" section of the same file (which does say "In the terminal that is already open in your Codespace, run: gh copilot").
Failure mode classification
Access barrier — the ambiguity is about which tool surface to use, not about a missing concept.
Quantitative guardrail
- Current
overall_score for 07-your-first-workflow.md: not in the bottom-8 list (estimated mid-range, ~6.0/10 based on corpus mean); this repair should not lower it.
- Weakest rubric dimension:
checkpoint_quality (0.0, shared rubric-wide artifact) — unaffected by this change.
- Current learning KPI dimensions for this step:
active_learning and scaffolding should stay flat or improve, since the change adds a concrete decision point (a scaffolding aid) without removing any existing practice.
- This is a clarifying addition, not a simplification of content — it should not reduce cognitive load below what the step already requires.
Acceptance criteria
Suggested owner
workshop maintainer (content edit with copilot coding agent assist for wording)
Related to #3478
Generated by 🔬 Workshop Student Simulator · copilot · auto · 131.4 AIC · ⌖ 7.67 AIC · ⊞ 15.2K · ◷
Problem statement
Step 7 (
07-your-first-workflow.md) tells learners to "run this prompt" in your AI agent without naming a specific surface (Copilot CLI vs. VS Code Copilot Chat vs. the Agents-tab prompt box). The Monte Carlo simulation shows this step is now the top dropout driver (23.5% conditional dropout among 22,269 at-risk runs), split betweencopilot-access-missing(3,762 failures) andworkflow-authoring-friction(1,471 failures).tool: CCAlearners are disproportionately affected because they must independently translate the generic phrase into the Agents-tab flow.Proposed change
Add one short, explicit branch immediately before the authoring prompt block that names the exact surface per
toolpreference (Copilot CLI command, VS Code Copilot Chat panel, or GitHub Agents tab), mirroring the pattern already used correctly in the earlier "Verify Copilot access" section of the same file (which does say "In the terminal that is already open in your Codespace, run:gh copilot").Failure mode classification
Access barrier — the ambiguity is about which tool surface to use, not about a missing concept.
Quantitative guardrail
overall_scorefor07-your-first-workflow.md: not in the bottom-8 list (estimated mid-range, ~6.0/10 based on corpus mean); this repair should not lower it.checkpoint_quality(0.0, shared rubric-wide artifact) — unaffected by this change.active_learningandscaffoldingshould stay flat or improve, since the change adds a concrete decision point (a scaffolding aid) without removing any existing practice.Acceptance criteria
overall_scorefor07-your-first-workflow.mdstays flat or improves after the change(2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5stays flat or improvescopilot-access-missingandworkflow-authoring-frictionfailure counts for07-first-workflowdecrease in a rerunSuggested owner
workshop maintainer(content edit withcopilot coding agentassist for wording)Related to #3478