project-backlog

Project Backlog

Turn repository-review findings into deduplicated, ordered issue drafts; discovery and drafting are read-only, and github-issues owns the authorized creation of each issue.

Workflow

1. Confirm the target: Read the local repository and its instructions with git, then resolve the candidate with gh repo view --json nameWithOwner,visibility; show it to the user without treating discovery as mutation authorization.
2. Review: Run the cross-cutting repository review; keep partial scans and unavailable services as evidence gaps.
3. Read existing issues: Fetch the open and closed issues needed for duplicate analysis with complete bodies, comments, labels, state, and native blockedBy and blocking relationships; search by the underlying problem and evidence, not title similarity.
4. Research sparingly: Consult primary documentation or upstream source only where it materially confirms a retained finding; record the version context and separate sourced fact from inference.
5. Classify: Mark each candidate a verified finding or a trend opportunity; a trend becomes an issue only when current project evidence proves fit and value.
6. Reject: Drop candidates that duplicate an existing issue, lack reproducible evidence, exceed the project's likely value, restore rejected scope, or add unjustified complexity.
7. Draft: Write every retained item with the draft contract; explain why it is distinct from each close match and model dependencies as draft-to-draft or draft-to-issue edges.
8. Stop at the gate: Present deduplication decisions, ordered drafts, and the dependency graph; proceed only when the user explicitly authorizes creation in the confirmed repository, which is the only mutation target.
9. Create issues: Refresh visibility, labels, matching issues, and native dependencies immediately before writing and stop if drafts went stale; create each issue in draft order through github-issues and record draft ID, issue number, node ID, and URL after each success.
10. Add edges: Only after every node exists, read current relationships and add the missing ones with the addBlockedBy mutation from the draft contract; never encode a dependency only in prose.
11. Verify: Read back every body, label set, and blockedBy and blocking relationship from GitHub before claiming completion.
12. Report: Return these sections in order.
    • Review evidence: highest proven rung of the proof ladder and material gaps.
    • Deduplication: candidate-to-existing-issue decisions and distinctness rationale.
    • Draft backlog: ordered drafts with routing and dependency edges.
    • Authorization gate: exact repository and mutations awaiting approval, or the authorization already received.
    • Mutation receipt: only after authorized writes; created issues, labels, verified native edges, and any partial state.