-
Notifications
You must be signed in to change notification settings - Fork 40
feat(agents): add GitHub backlog management pipeline #448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
@katriendg @agreaves-ms — Would appreciate your perspective on this pipeline ... this is what I've been using to do backlog management for hve-core, edge-ai, and robotics. Key areas where input would be valuable:
This mirrors the ADO pipeline architecture — feedback from that experience would help shape the GitHub-native adaptation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Adds a GitHub-native backlog management pipeline (orchestrator agent + prompts + instructions) to mirror the existing ADO planning/execution architecture, and deprecates the legacy github-issue-manager agent in favor of a multi-stage workflow (triage, discovery, sprint planning, execution).
Changes:
- Introduces the
github-backlog-managerorchestrator agent and four workflow entry-point prompts (triage, discovery, sprint planning, execution). - Adds a P0 planning reference specification plus workflow-specific instructions (triage/discovery/update) and community interaction templates.
- Updates extension/docs/manifests to reference the new agent and fixes the
github-add-issueprompt to usemcp_github_issue_write.
Reviewed changes
Copilot reviewed 19 out of 19 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/agents/github-backlog-manager.agent.md | New orchestrator that classifies intent and dispatches to backlog workflow prompts |
| .github/instructions/github-backlog-planning.instructions.md | P0 reference spec for templates, tool catalog, directory conventions, and autonomy model |
| .github/instructions/github-backlog-triage.instructions.md | Triage workflow spec (labels/milestones/duplicate detection) producing triage plans |
| .github/instructions/github-backlog-discovery.instructions.md | Discovery workflow spec supporting user-centric, artifact-driven, and search-based modes |
| .github/instructions/github-backlog-update.instructions.md | Batch execution spec for handoff-driven issue mutations with resumable logs |
| .github/instructions/community-interaction.instructions.md | Community-facing comment tone + scenario templates for GitHub-visible interactions |
| .github/prompts/github-triage-issues.prompt.md | Entry prompt for triaging needs-triage issues into a reviewable plan |
| .github/prompts/github-discover-issues.prompt.md | Entry prompt for discovery across the three supported discovery paths |
| .github/prompts/github-execute-backlog.prompt.md | Entry prompt for executing handoff plans (create/update/link/close/comment) |
| .github/prompts/github-sprint-plan.prompt.md | Entry prompt for milestone sprint planning + optional execution |
| .github/prompts/github-add-issue.prompt.md | Refactored standalone issue creation prompt; fixes tool name to mcp_github_issue_write |
| .github/agents/github-issue-manager.agent.md | Deprecated legacy agent with migration notice |
| .github/CUSTOM-AGENTS.md | Updates agent catalog/docs to reference the new backlog manager |
| .github/agents/hve-core-installer.agent.md | Updates installer copy and agent listings to include the new backlog manager |
| .github/instructions/writing-style.instructions.md | Adds community interaction guidance references and table updates |
| docs/getting-started/install.md | Updates getting-started references to the new GitHub agent |
| docs/getting-started/mcp-configuration.md | Updates MCP dependency table for the new GitHub agent |
| extension/README.md | Updates extension agent listing to github-backlog-manager |
| extension/package.json | Regenerates extension manifest to include new agent/prompts/instructions |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #448 +/- ##
=======================================
Coverage 76.22% 76.22%
=======================================
Files 20 20
Lines 3503 3503
=======================================
Hits 2670 2670
Misses 833 833
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
- add 4 instructions, 4 prompts, 1 agent for TPM-focused backlog management - fix mcp_github_create_issue tool reference in github-add-issue.prompt.md - add community-interaction.instructions.md and update writing-style registry - regenerate extension/package.json to register all new artifacts 🤖 Generated by Copilot
3fe2c00 to
c5ea426
Compare
…ption 🔧 - Generated by Copilot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 19 out of 19 changed files in this pull request and generated 5 comments.
…unity interaction - align tracking path table with planning spec scope conventions - remove opaque Decision D1 policy exemption note - remove undocumented pull_request_review_write tool reference 🔧 - Generated by Copilot
…ackaging - add extension:prepare:prerelease and extension:package:prerelease npm scripts - update PACKAGING.md with prerelease commands in prepare, package, and pre-release sections 📦 - Generated by Copilot
…lassified issues - add Comment operation to planning handoff template and field matrix - retain needs-triage on unclassified issues across all autonomy tiers - create planning folder for all discovery paths, not just Path B - update execution priority to include Comment after Close 🏷️ - Generated by Copilot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 21 out of 21 changed files in this pull request and generated 5 comments.
651c968 to
f7e3dcf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 21 out of 21 changed files in this pull request and generated 2 comments.
…nteraction templates - set stale issue closure period to 74 days (60-day stale + 14-day grace) - set stale PR closure period to 21 days (14-day stale + 7-day grace) 🔧 - Generated by Copilot
- change handoff prompt values from filenames to slash commands - fix template blockquote links to use absolute URLs with owner/repo vars - add execution as a valid planning type in backlog planning spec 🔧 - Generated by Copilot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 21 out of 21 changed files in this pull request and generated 3 comments.
## Description Defines inactivity closure policies for issues, discussions, and pull requests to reduce noise from stale items. **Issue and discussion policy** (GOVERNANCE.md) — Issues inactive for 60 days receive a `stale` label and warning comment. If no activity follows within 14 days (74 days total), the issue is closed as `not_planned` with a `closed-stale` label. Exemptions: `pinned`, `security`, `do-not-close`, and milestone-assigned issues. Discussions follow the same thresholds with manual enforcement until tooling supports automation. **Pull request policy** (CONTRIBUTING.md) — Active PRs waiting on the author for 14 days receive a `stale` label. If no author activity follows within 7 days (21 days total), the PR is closed. Draft PRs are fully exempt. Additional exemptions: `do-not-close` and `waiting-on-reviewer` labels. ### Policy Summary | Scope | Stale After | Grace Period | Total | Exemptions | | :---- | :---------- | :----------- | :---- | :--------- | | Issues | 60 days | 14 days | 74 days | `pinned`, `security`, `do-not-close`, milestone-assigned | | Discussions | 60 days | 14 days | 74 days | Same as issues (manual enforcement) | | Active PRs | 14 days | 7 days | 21 days | draft, `do-not-close`, `waiting-on-reviewer` | Six supporting labels have been pre-created on the repository: `stale`, `closed-stale`, `do-not-close`, `pinned`, `waiting-on-author`, `waiting-on-reviewer`. ## Related Issue(s) - Closes #442 - Closes #443 ## Type of Change ### Code & Documentation - [ ] Bug fix (non-breaking change that fixes an issue) - [ ] New feature (non-breaking change that adds functionality) - [x] Documentation update - [ ] Breaking change (fix or feature that would cause existing functionality to change) ### Infrastructure - [ ] CI/CD pipeline changes - [ ] Build system changes - [ ] Configuration changes ### AI Artifacts - [ ] Copilot instructions (`.instructions.md`) - [ ] Copilot prompt (`.prompt.md`) - [ ] Copilot agent (`.agent.md`) - [ ] Skill package (`SKILL.md`) ### Other - [ ] Refactoring (no functional changes) - [ ] Performance improvement - [ ] Test changes only ## Testing - Verified cross-references between GOVERNANCE.md and CONTRIBUTING.md resolve correctly - Confirmed 6 GitHub labels exist on the repository - Markdown linting passes ## Checklist ### Required Checks - [x] I have read the [CONTRIBUTING](../CONTRIBUTING.md) document - [x] My changes follow the project coding standards - [x] I have updated documentation accordingly - [x] All new and existing linting checks pass ### Required Automated Checks - [x] Markdown linting: `npm run lint:md` - [x] Frontmatter validation: `npm run lint:frontmatter` ## Security Considerations - No secrets, tokens, or credentials introduced - No new dependencies added - No changes to CI/CD workflows or GitHub Actions - All changes are documentation only ## Additional Notes This PR is intentionally scoped to the governance and contributor documentation changes for inactivity policies. The community interaction message templates (Scenario 10 and 11 time-period values) are tracked separately alongside the backlog management pipeline in PR #448.
…anagement-tooling
…og instructions
- remove Inputs sections from discovery, triage, and update instructions
- replace body `${input:}` references with plain parameter names
- align update instructions to use `handoff` matching prompt canonical name
🔧 - Generated by Copilot
Description
Introduces a complete TPM-focused GitHub backlog management pipeline — 1 orchestrator agent, 5 instructions (including P0 reference specification), and 4 entry-point prompts — mirroring the ADO tooling pipeline architecture with GitHub-native MCP tools. Replaces and deprecates the single-purpose
github-issue-manageragent with a four-stage workflow covering triage, discovery, sprint planning, and batch execution.Also fixes a bug in
github-add-issue.prompt.mdwhere the prompt referenced non-existentmcp_github_create_issue(correct tool:mcp_github_issue_write).Architecture
Instructions-first pipeline parallels the ADO tooling suite:
Key design decisions:
github-backlog-planning.instructions.mddefines planning file templates, MCP tool catalog, search protocols, similarity assessment matrix, state persistence, and the three-tier autonomy model. All workflow instructions cross-reference this specification.New Artifacts (10 files)
github-backlog-manager.agent.mdgithub-backlog-planning.instructions.mdgithub-backlog-triage.instructions.mdgithub-backlog-discovery.instructions.mdgithub-backlog-update.instructions.mdcommunity-interaction.instructions.mdgithub-triage-issues.prompt.mdgithub-discover-issues.prompt.mdgithub-execute-backlog.prompt.mdgithub-sprint-plan.prompt.mdModified Files (9)
github-add-issue.prompt.mdmcp_github_create_issue→mcp_github_issue_write; rewritten 304→86 lines; maturity→experimentalgithub-issue-manager.agent.md[!CAUTION]migration noticeCUSTOM-AGENTS.mdgithub-issue-manager→github-backlog-managerhve-core-installer.agent.mdwriting-style.instructions.mddocs/getting-started/install.mddocs/getting-started/mcp-configuration.mdextension/README.mdextension/package.jsonRelated Issue(s)
Closes #447
Type of Change
Select all that apply:
Code & Documentation:
Infrastructure & Configuration:
AI Artifacts:
prompt-builderagent and addressed all feedback.github/instructions/*.instructions.md).github/prompts/*.prompt.md).github/agents/*.agent.md).github/skills/*/SKILL.md)Other:
.ps1,.sh,.py)Sample Prompts (for AI Artifact Contributions)
Triage Workflow
User Request:
Execution Flow:
github-triage-issues.prompt.mdgithub-backlog-triage.instructions.md+ planning specificationmcp_github_list_issuestriage-plan.mdunder.copilot-tracking/github-issues/triage/Output Artifacts:
Success Indicators:
.copilot-tracking/github-issues/Discovery Workflow
User Request:
Execution Flow:
github-discover-issues.prompt.mdmcp_github_search_issuesfor overlapissues-plan.mdwith new issues to create and existing ones to updateSuccess Indicators:
Testing
All 6 validators passed clean on committed artifacts:
npm run format:tablesnpm run lint:frontmatternpm run lint:mdnpm run spell-checknpm run lint:md-linksnpm run extension:prepareChecklist
Required Checks
AI Artifact Contributions
/prompt-analyzeto review contributionprompt-builderreviewRequired Automated Checks
The following validation commands must pass before merging:
npm run lint:mdnpm run spell-checknpm run lint:frontmatternpm run lint:md-linksnpm run lint:psSecurity Considerations
No new dependencies introduced. No authentication or secret changes. All artifacts are declarative markdown — no executable code added.
Additional Notes
Branch Drift
This branch is based on commit
25b34dewhich predates several changes now onmain(version rollback 2.2.0→2.1.0, deletedincident-response.prompt.md,rca-template.md,copyright-headers.yml). The PR diff shows 14 additional files not part of this feature work. A rebase onto currentmainbefore merge will isolate the feature delta to the 19 files listed above.Design Rationale
The instructions-first architecture follows the proven ADO pipeline pattern where a single P0 reference specification (758 lines) defines all shared conventions and specialized workflow instructions cross-reference rather than duplicate. Each prompt file stays focused (<130 lines) while the orchestrator agent handles intent classification and routing.