Individual skill
repo-harness-issue-flow
Run GitHub issue and PR driven development with several agents. Use it to turn a PRD or feature into a backlog of requirement issues split by architecture module, with sub-issue and blocked-by links and boundaries; to dispatch workers and follow their PRs and CI to merge as coordinator; or, as a worker, to deliver a dispatched issue's PR, raise a boundary question, hand off or take over a stalled claim, or sync a PR stacked on another agent's PR. Exclude PRD drafting, code review, and small changes that need no issue.
assets/skills/repo-harness-issue-flow/SKILL.md
Source commit f27ddc483e189f1bb81af6d9334cf3c5501a8349
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 435
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-workflows Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codegraph Repository topic
- codex Repository topic
- developer-tools Repository topic
- typescript Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,446 bytesSKILL.mdcore · 8,446 bytesreferences/acceptor.mddoc · 7,960 bytesreferences/board.mddoc · 17,768 bytesreferences/events.mddoc · 6,465 bytesreferences/orchestrator.mddoc · 27,934 bytesreferences/replan.mddoc · 4,370 bytesreferences/templates.mddoc · 18,395 bytesreferences/worker.mddoc · 12,670 bytes
Read excerpt
# repo-harness-issue-flow
Bot entrypoint. Issue/PR driven development (IPDD). GitHub holds the coordination state.
No local plan, task, review or notes file holds task state.
## Why this flow works
An orchestrator that sees the whole architecture writes each requirement
once, in a GitHub issue, with its module, dependencies and boundaries. A
worker then needs only the issue URL to start. The PR and CI record the
proof, and every agent and person reads the same state.
The boundary text carries most of the value. A worker that meets an open
question fills it. Over-defensive models fill it with fallbacks, aliases,