Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[workshop-sim] Improve: Convert the passive "Three key terms" table in 05-agentic-workflows-intro.md into an active-recall exercise

Open Beginner friendly
  • Is something wrong?
#4,218 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
content

Research direction

Read 05-agentic-workflows-intro.md, especially the “Three key terms” section and the existing <details> reveal pattern in Activities 1–3. Convert the table into a matching or labeling exercise with a reveal, keeping all three terms and definitions. Confirm Activities 1–3 and the checklist are unchanged, then check that the shared quantitative assessment and learning KPI index stay flat or improve.

Written by the indexing model from the issue text.

Description

feedback simulation workshop

Problem statement

05-agentic-workflows-intro.md (simulator step 05-agentic-intro) is the second-highest-dropout step in the workshop (18.4% conditional dropout among 36,678 at-risk runs, 95% interval 18.0%–18.8%). Failures split between agentic-concept-gap (4,609) and deployment-capability-gap (2,128). Notably, the Monte Carlo breakdown shows experienced actions-user learners also stall here (not just beginners), suggesting the "Three key terms" table (Trigger / Task brief / Safe outputs) is introduced too passively — as a table to read — before the page's own later activities (Activity 1, 2, and 3) ask learners to actively apply the same three terms.

Proposed change

Convert the passive "Three key terms" table into a short matching/labeling micro-activity: present the three terms and their definitions in scrambled order and ask the learner to match each term to its definition before revealing the answer (reusing the existing <details>/reveal pattern already used elsewhere on this same page for Activities 1–3). This moves active recall earlier in the page instead of only appearing in the later, more complex activities.

Failure mode classification

Learning barrier — conceptual density without sufficient early active-recall scaffolding, not an access or tooling problem.

Quantitative guardrail

Current scores for 05-agentic-workflows-intro.md:

  • overall_score: 5.43/10
  • Weakest rubric dimensions: active_learning 2.4/10 (lowest active_learning score of any step in the corpus) and checkpoint_quality 0.0/10
  • Learning KPI index for this step: active_learning 2.4, checkpoint_quality 0.0, scaffolding 5.0 → index = (2.0×2.4 + 2.0×0.0 + 1.5×5.0)/5.5 = 2.24/10

Replacing a static table with a matching/reveal micro-activity directly targets active_learning (the lowest-scoring dimension on this page) without removing any existing content, activity, or checkpoint item — it should raise overall_score and the learning KPI index for this file, not lower them.

Acceptance criteria

  • The shared curriculum quantitative assessment overall_score for 05-agentic-workflows-intro.md stays flat or improves after the change
  • The step's learning KPI index (2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5 stays flat or improves for 05-agentic-workflows-intro.md
  • Activities 1, 2, and 3 and the existing end-of-page checklist remain unchanged and are not removed or weakened
  • The "Three key terms" section is converted to a matching/reveal micro-activity (using the page's existing <details> reveal pattern) rather than a static table, without reducing the number of terms or definitions covered

Suggested owner

copilot coding agent
Related to #4215

Generated by 🔬 Workshop Student Simulator · copilot · auto · 191.3 AIC · ⌖ 7.49 AIC · ⊞ 15.1K · ◷

  • expires on Oct 6, 2026, 7:27 AM UTC
Dominant language
JavaScript
Stars
51
Forks
23
Avg merge
9h 52m
Merged PRs (30d)
26

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.