New skill: issue_prioritization_workflow, prioritize issues with a coding agent and GitHub Projects or GitLab

Abierto
  • ¿Algo no está bien?
#4 1 comentario 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, gitlab
Área
devtools

Línea de trabajo

Read the first comment for the full process summarized by the issue, then inspect the existing bug_triage_workflow skill to understand the project’s skill conventions. Define how the skill handles the listed open questions about GitHub Projects, GitLab, objectives, scoring, and queue size; done means a SKILL.md for issue_prioritization_workflow that proposes priorities and a ranked Ready queue for approval before updating a board.

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

Descripción

Goal

Create a new skill, with its instructions in SKILL.md, that lets a coding agent prioritize the open issues of a repository and keep that priority order in the project board of the issue tracker.

  • The coding agent estimates the impact, the urgency, and the effort of each open issue, and finds the dependencies and the blockers between issues.
  • The coding agent proposes a priority level (P0, P1, P2, P3) and an explicitly ranked Ready queue, and explains each choice in one or two sentences.
  • The developer approves the proposed priorities and the proposed ranking before the coding agent changes any issue or any project board.
  • The coding agent writes the approved priorities and the approved ranking to GitHub Projects, or to the equivalent feature in GitLab.
  • The developer can run the skill again whenever the objectives change, or once a week, to keep the priority order current.

The full process is summarized in the first comment of this issue.

Proposed name

issue_prioritization_workflow

Proposed description

Prioritize the open issues of a repository and keep a ranked Ready queue in GitHub Projects or in the equivalent feature in GitLab. Use when the developer asks which issue to work on next, asks to assign priorities, or asks to update the project board. Propose every priority and every ranking first, and change issues or project boards only after the developer approves.

Open questions

  1. Which GitLab feature is the equivalent of GitHub Projects: issue boards with scoped labels (for example priority::1), the issue weight field for the effort, or epics? Do these features need a paid GitLab tier?
  2. Where does the skill store the priority level and the effort in a personal GitHub repository: in custom fields of GitHub Projects, or in labels? Does the native Priority field and the native Effort field of GitHub issues apply only to organization repositories?
  3. How does the skill store the explicit ranking of the Ready queue: the item order of a GitHub Projects view, a number field, or a pinned issue that lists the queue?
  4. Does the skill use the gh command line and the glab command line, or a Model Context Protocol server for GitHub and for GitLab?
  5. How does the skill learn the current objectives of the project: from the developer in the conversation, from a file in the repository, or from a milestone?
  6. Does the skill keep the formula Score = (Impact × Urgency) / Effort, or only use the three estimates as input for the judgment of the coding agent?
  7. How does this skill relate to the existing bug_triage_workflow skill: does the new skill replace it, call it, or stay separate and cover all issue types?
  8. What is the maximum size of the Ready queue: ten issues, as the source suggests, or a number that the developer chooses?

Source

https://chatgpt.com/c/6ad9d01f-a480-83ed-bef3-e98d23ac1e04

Lenguaje dominante
Sin datos de lenguaje
Estrellas
1
Forks
0
Merge medio
10 min
PR fusionados (30 d)
11

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 jeromeetienne/coding_agent_plugin

Todos los issues de jeromeetienne/coding_agent_plugin

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.