Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[workshop-sim] Improve: Add intermediate checkpoints to What Are Agentic Workflows? to close the agentic-concept-gap

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#4,089 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
84/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Área
documentation

Línea de trabajo

Abre 05-agentic-workflows-intro.md y revisa las tres actividades existentes y la lista de comprobación actual al final de la página. Añade una breve autoevaluación puntuable después de cada actividad, que cubra las funciones de los archivos, la clasificación de tareas y los criterios del resumen de la tarea, conservando el contenido existente. Confirma que las puntuaciones del currículo compartido y el KPI de aprendizaje se mantienen o mejoran.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feedback simulation workshop
Problem statement

05-agentic-workflows-intro.md has the lowest active_learning score in the curriculum (2.4/10) and zero checkpoint_quality, and it is the third-highest-dropout step at 18.71% conditional dropout (37,149 at-risk runs), with agentic-concept-gap as the dominant failure category. The page has three good activities (file labeling, task classification, brief-writing) but only a single end-of-page checklist — a learner who stumbles on Activity 1 (the two-file structure) gets no signal until the final checkpoint, by which point they may already be lost on the core trigger/task-brief/safe-outputs concept.

Proposed change

Add a short scored self-check immediately after each of the three existing activities (not just at the end of the page), so a learner gets immediate feedback on whether they correctly identified the .md/.lock.yml roles, classified Task A/B correctly, and met the three task-brief criteria — before moving to the next activity. This adds checkpoints; it does not remove any existing content or activity.

Failure mode classification

Learning barrier — low active_learning and zero checkpoint_quality indicate a scaffolding gap, not an access/environment problem.

Quantitative guardrail

Current scores for 05-agentic-workflows-intro.md: overall_score 5.43/10 (lowest in Part 1 alongside 04-github-actions-intro.md), active_learning 2.4, checkpoint_quality 0.0, scaffolding 5.0 → learning KPI index 2.00/10 (lowest of the three steps prioritized in this simulation). Because the proposed change adds intermediate checkpoints and keeps existing activities intact, it should raise checkpoint_quality and active_learning directly while not lowering scaffolding, overall_score, or the KPI index. Do not resolve this by simplifying or removing the three-key-terms table or activities — the dropout here is a scaffolding gap, not excess difficulty.

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
  • Hands-on practice, checkpoints, and scaffolding are preserved or strengthened (not removed or weakened to chase completion numbers)
  • Each of the three existing activities (file-identification, task classification, brief-writing) has its own intermediate check, in addition to the existing end-of-page checklist
Suggested owner

copilot coding agent
Related to #4087

Generated by 🔬 Workshop Student Simulator · copilot · auto · 197.6 AIC · ⌖ 7.17 AIC · ⊞ 15.1K · ◷

  • expires on Oct 3, 2026, 9:02 AM UTC
Lenguaje dominante
JavaScript
Estrellas
53
Forks
35
Merge medio
1 d 6 h
PR fusionados (30 d)
15

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/gh-aw-workshop

Todos los issues de githubnext/gh-aw-workshop

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.