issue-batch-orchestrator
Analyze multiple GitHub Issues and produce safe parallel and sequential execution waves with review gates.
소스 정보
- 저장소
- ehuerta6/cappy-code
- 최근 소스 활동
- 2026년 10월 6일 05:13
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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
GitHub에서 보기