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

[workshop-sim] Improve: Add worked safe-outputs artifact activity to Step 5

Abierto Apto para principiantes
  • ¿Algo no está bien?
#4,495 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
75/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, javascript, yaml
Área
documentation

Línea de trabajo

Empieza leyendo 05-agentic-workflows-intro.md y localiza «Activity 2 — agentic or standard?» y Activity 3. Añade entre ambas un ejercicio breve que indique a los alumnos que consulten un .lock.yml de ejemplo y les pida encontrar la medida de protección safe-outputs. Se considerará terminado cuando las puntuaciones cuantitativas se mantengan o mejoren, y las actividades existentes y la lista de verificación final sigan intactas.

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 second-highest conditional dropout (19.6%, 7,717 of 39,460 at-risk runs), dominated by agentic-concept-gap (5,472 failures) and deployment-capability-gap (2,245 failures). The page's active_learning rubric score is only 2.4/10 — the lowest of any top-5 dropout step — even though it already contains three "Activity" blocks and a two-file (.md/.lock.yml) prediction exercise. The activities are mostly reveal/predict exercises without a worked example that ties the abstract "agentic vs. standard" distinction to a concrete artifact the learner can inspect in their own repository.

Proposed change

Add one additional hands-on micro-activity immediately after "Activity 2 — agentic or standard?": have the learner open a real .lock.yml file from a sample agentic workflow (link to an example in githubnext/gh-aw-workshop or a generated sample) and find the specific YAML block that encodes the task brief's safe-outputs guardrail, connecting the abstract safe-outputs term to a concrete repository artifact before Activity 3's task-brief-writing exercise. This increases hands-on activity density (activity_density) without adding conceptual density (no new terms), which should raise active_learning directly.

Failure mode classification

Learning barrier (conceptual density / insufficient scaffolding connecting abstract terms to concrete artifacts — not an access or tooling issue).

Quantitative guardrail

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

  • overall_score: 5.43/10
  • Weakest rubric dimensions: checkpoint_quality (0.0/10) and active_learning (2.4/10)
  • Learning KPI index: 2.24/10 (active_learning 2.4, checkpoint_quality 0.0, scaffolding 5.0)

The proposed change adds one concrete, code-block-based activity (raising activity_density and thus active_learning) without adding new vocabulary (so cognitive_load's new_concepts penalty does not worsen) and without removing the existing checklist or prerequisite section (checkpoint_quality and scaffolding unaffected). overall_score and the learning KPI index should therefore improve, not just completion.

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 — the three existing activities and the final checklist remain intact
  • The new activity links an abstract term (safe outputs) to a concrete, inspectable .lock.yml artifact and does not introduce new unexplained vocabulary

Suggested owner

copilot coding agent
Related to #4493

Generated by 🔬 Workshop Student Simulator · copilot · auto · 309.7 AIC · ⌖ 14.8 AIC · ⊞ 15.1K · ◷

  • expires on Oct 13, 2026, 8:28 AM UTC
Lenguaje dominante
JavaScript
Estrellas
52
Forks
26
Merge medio
12 h 58 min
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.