issue-batch-orchestrator
Analyze multiple GitHub Issues and produce safe parallel and sequential execution waves with review gates.
Datos de origen
- Repositorio
- ehuerta6/cappy-code
- Última actividad en el origen
- 6 de octubre de 2026 a las 05:13
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 1
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- issue-batch-orchestrator
- description
- Analyze multiple GitHub Issues and produce safe parallel and sequential execution waves with review gates.
# Issue batch orchestrator
Plan execution for a batch of GitHub Issues.
## Process
1. Read every issue and relevant project context.
2. Inspect enough code to estimate dependencies and overlapping change surfaces.
3. Classify issues as prerequisite, independent, overlapping, deployment, or documentation work.
4. Build execution waves using maximum safe parallelism.
5. Add merge or deployment gates between dependent waves.
6. Generate one concise operational prompt for the batch orchestrator.
## Rules
- Issues are scope contracts.
- Dependent work starts after prerequisites merge.
- Parallel issues must be genuinely independent.
- Use one branch and PR per issue unless the repo says otherwise.
- Implementers stop at READY FOR REVIEW.
- Independent review controls merge readiness.
- Recheck parallel PRs after sibling PRs merge.
- Documentation sync normally runs last.
- External blockers stop dependent work.
- Do not redesign around blockers.
## Return
- dependency graph
- execution waves
- blockers and gates
- executable orchestrator prompt
Ver en GitHub