feat: GitHub issue triage system with /triage command

[joshsmithxrm]

Summary

Implements a comprehensive GitHub issue triage system for the PPDS ecosystem:

• /triage slash command for batch issue categorization
• Issue templates (feature_request.yml, bug_report.yml) for consistent structure
• ROADMAP.md documentation with triage guidelines, field definitions, and sizing criteria
• Label taxonomy cleanup (removed 6 deprecated, added 7 area labels)
• CLAUDE.md updates to reference roadmap and triage process

Integrates with the PPDS Roadmap project (#3) to assign Type, Priority, Size, Status, and Target fields to issues.

Changes

Triage Command

• .claude/commands/triage.md - Complete batch triage workflow:
  1. Fetch issues and project items via GitHub CLI/GraphQL
  2. Identify untriaged issues (missing any field)
  3. Present summary table for user review
  4. Generate editable markdown table for field assignments
  5. Validate inputs and bulk update via GraphQL
  6. Report results

Documentation

• docs/ROADMAP.md - NEW comprehensive triage guide (500+ lines)
  • Project field definitions (Type, Priority, Size, Status, Target)
  • Sizing guidelines (XS < 4h, S < 1d, M < 3d, L < 1w, XL > 1w)
  • Label taxonomy and usage rules
  • Target field strategy (relative values: This Week, Next, Q1 2026, etc.)
  • Project views and best practices
• docs/FEATURE_ROADMAP.md - MOVED from ROADMAP.md (preserves existing phase planning)
• CLAUDE.md - Added Issue Triage section with field table and label strategy
• C:\VS\ppds\CLAUDE.md - Added roadmap reference (workspace level)

Issue Templates

• .github/ISSUE_TEMPLATE/feature_request.yml - Feature template (Summary, Motivation, Acceptance Criteria, etc.)
• .github/ISSUE_TEMPLATE/bug_report.yml - Bug template (Description, Steps to Reproduce, Environment, etc.)
• .github/ISSUE_TEMPLATE/config.yml - Disable blank issues, direct questions to Discussions

Label Changes (via GitHub CLI)

Removed (6): priority: p1, help wanted, good first issue, invalid, wontfix, duplicate
Added (7): area:plugins, area:data, area:auth, area:cli, area:tui, area:pooling, area:daemon

Test Plan

• All files created/modified successfully
• Commits follow project conventions
• Test /triage command on actual issues
• Verify issue templates work for new issues
• Verify ROADMAP.md renders correctly on GitHub
• Run bot reviews and address findings

Related

• PPDS Roadmap project: PPDS Roadmap
• Project made public for OSS transparency

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @joshsmithxrm, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes a robust issue triage and project management system for the PPDS ecosystem. It introduces a new slash command to streamline issue categorization, standardizes issue submission through new templates, and provides comprehensive documentation on how to effectively manage issues within the GitHub project. The changes aim to bring consistency and efficiency to the project's workflow.

Highlights

• New /triage Command: Introduces a powerful /triage slash command for batch categorization of GitHub issues, integrating with the PPDS Roadmap project to assign Type, Priority, Size, Status, and Target fields.
• Enhanced Issue Templates: Adds structured feature_request.yml and bug_report.yml issue templates, along with a config.yml to disable blank issues and guide users to discussions.
• Comprehensive Triage Documentation: A new ROADMAP.md document provides extensive guidelines for issue triage, including project field definitions, sizing criteria, label taxonomy, and best practices for project views.
• Refined Label Taxonomy: Cleans up existing labels by removing 6 deprecated ones and adding 7 new area: labels for better categorization.
• CLAUDE.md Integration: Updates CLAUDE.md to include a new "Issue Triage" section, referencing the roadmap and the new triage process.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces an impressive and comprehensive issue triage system, complete with a /triage command specification, detailed ROADMAP.md documentation, and new issue templates. The level of detail in the process definition is excellent. My review focuses on improving the clarity, consistency, and effectiveness of the /triage command documentation, particularly for AI consumption.

[Copilot]

Pull request overview

This PR implements a comprehensive GitHub issue triage system for the PPDS ecosystem, introducing a /triage command for batch issue categorization, structured issue templates, and extensive documentation.

Key Changes:

• New /triage slash command for systematic batch issue categorization with project field assignment
• Comprehensive triage documentation in docs/ROADMAP.md (612 lines) with field definitions, sizing guidelines, and best practices
• GitHub issue templates (feature_request.yml, bug_report.yml) for consistent issue creation

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
docs/ROADMAP.md	NEW comprehensive triage guide with project fields, label strategy, workflow, and best practices
docs/FEATURE_ROADMAP.md	MOVED from original ROADMAP.md; preserves phase planning and extension parity epic content
CLAUDE.md	Added Issue Triage section with project fields table, label strategy, and /triage command reference
.claude/commands/triage.md	NEW complete /triage command documentation with GraphQL queries, workflow, and implementation notes
.github/ISSUE_TEMPLATE/feature_request.yml	NEW feature request template with Summary, Motivation, Acceptance Criteria, and Implementation Notes
.github/ISSUE_TEMPLATE/bug_report.yml	NEW bug report template with Description, Steps to Reproduce, Expected/Actual Behavior, and Environment
.github/ISSUE_TEMPLATE/config.yml	NEW configuration to disable blank issues and redirect questions to Discussions

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.