Add jira-issue-triage (v1.4.0), azure-issue-triage (v0.5.0), and azure-incident-postmortem (v0.1.0) plugins#39
Open
TahaBikanerwala wants to merge 19 commits into
Open
Add jira-issue-triage (v1.4.0), azure-issue-triage (v0.5.0), and azure-incident-postmortem (v0.1.0) plugins#39TahaBikanerwala wants to merge 19 commits into
TahaBikanerwala wants to merge 19 commits into
Conversation
Adds the jira-issue-triage plugin: an end-to-end Jira triage subagent across all archetypes (Bug, Incident, Feature, Task, Spike) with a /jira-issue-triage:setup wizard and three bundled skills (issue-investigator, requirements-investigator, jira-ticket-refiner). Registers the plugin in .claude-plugin/marketplace.json and adds it to the root README. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
….1.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…nt; bump to v1.2.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…o v1.3.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…e command Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… flight) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…gle-SRE template Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ostmortem:setup command Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ugins Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ine command Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…in root README Adds azure-issue-triage and azure-incident-postmortem entries to the incubyte-plugins marketplace and rewrites the root README to cover both new plugins. The README now includes a Configure Azure DevOps MCP section that explains the Rolai-shaped .mcp.json shipped with each plugin and walks non-Rolai users through a project-root override (org slug, PAT scopes, server-name parity with the plugin install). Also updates the jira-issue-triage section to mention the new /jira-issue-triage:investigate-and-refine command shipped in v1.4.0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
TahaBikanerwala
changed the title
| "source": "./discovery", | ||
| "description": "End-to-end product discovery flow that produces a structured PRD" | ||
| }, | ||
| { |
Member
There was a problem hiding this comment.
version upgrade is required
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds three triage subagents to the Incubyte marketplace and updates the root README to cover them:
jira-issue-triage(v1.0.0 → v1.4.0). End-to-end Jira triage across all archetypes (Bug, Incident, Feature, Task, Spike). v1.4.0 adds a new lightweight slash command,/jira-issue-triage:investigate-and-refine.azure-issue-triage(v0.5.0, new). Sibling ofjira-issue-triagefor Azure DevOps Boards. Ports the same workflow across all six archetypes (Bug, Incident, User Story, Feature, Task, Spike) with platform-specific behaviour: WIQL queries, Area/Iteration paths, State+Reason transitions,Microsoft.VSTS.Common.Severity, SLA-drivenDueDate, Teams escalation routing, EM fallback, sprint placement, story-point estimation, and Azure Repos pull-request linking.azure-incident-postmortem(v0.1.0, new). Generates a Google-SRE-style blameless postmortem from an Azure DevOps incident work item. Gathers evidence from Teams, related AzDO items, Datadog logs, and Azure Repos merges; pauses for review; produces the document.Both Azure plugins ship a Rolai-shaped
.mcp.jsonthat auto-registers the official Microsoft Azure DevOps MCP. Non-Rolai users override locally; the root README walks through that override step by step.What the branch contains
Jira (v1.0.0 → v1.4.0)
feat(jira-issue-triage): introduce v1.0.0 pluginfeat(jira-issue-triage): wire prose-style into Phase 5 and bump to v1.1.0prose-stylegraduates from roadmap into the bundled skill setfeat(jira-issue-triage): split Phase 3 gate; archetype-gated assignment; bump to v1.2.0feat(jira-issue-triage): UX pass on Phase 3 confirmation gate; bump to v1.3.0description_preview_pause_secondsconfig keyfix(jira-issue-triage): triage-ux-pass review fixesfeat(jira-issue-triage): add /jira-issue-triage:investigate-and-refine commanddocs(jira-issue-triage): add worked examples for /investigate-and-refineAzure issue triage (mirrored from sibling marketplace, v0.5.0)
feat(azure-issue-triage): mirror plugin from marketplacejt-bikanerwala-marketplace(v0.1.0 → v0.4.0 history collapsed into one snapshot)feat(plugins): ship .mcp.json + userConfig in both azure-* pluginschore(plugins): mimic Rolai-shaped AzDO MCP config in both azure-* pluginsrolaillcorg,server/.envvia dotenvx)rename(mcp): give each plugin a distinct AzDO MCP server nameazure-devops-triageso it doesn't collide withazure-devops-postmortemfeat(azure-issue-triage): add /azure-issue-triage:investigate-and-refine commanddocs(azure): make the plug-and-play story explicit in both READMEsAzure incident postmortem (new plugin, v0.1.0)
chore(azure-incident-postmortem): scaffold plugin manifest (v0.1.0 in flight)feat(azure-incident-postmortem): add README and prose-style skill mirrorprose-styleskillfeat(azure-incident-postmortem): add incident-timeline-builder skillfeat(azure-incident-postmortem): add postmortem-writer skill with Google-SRE templatefeat(azure-incident-postmortem): add agent body and /azure-incident-postmortem:setup commandRepo docs
docs: register azure plugins in marketplace.json and document config in root README. Adds both Azure plugins to.claude-plugin/marketplace.json, rewrites the root README to cover them, and introduces a Configure Azure DevOps MCP section with explicit override steps for non-Rolai users.Highlights
prose-styleis bundled in every plugin, namespaced via plugin resolution, and applied to every piece of generated prose (refined titles, descriptions, comments, postmortem documents, Slack and Teams summaries).azure-devops-triageandazure-devops-postmortem) so both can be enabled at once without collision.Test plan
Marketplace install
/plugin marketplace add incubyte/ai-pluginssucceeds/plugin install jira-issue-triage@incubyte-pluginsinstalls cleanly/plugin install azure-issue-triage@incubyte-pluginsinstalls cleanly/plugin install azure-incident-postmortem@incubyte-pluginsinstalls cleanly.claude-plugin/marketplace.jsonlists all three plugins with the rightsourcepathsJira triage
/jira-issue-triage:setupruns and writes.claude/jira-issue-triage.config.jsonissue-investigator, pauses at Phase 3 gaterequirements-investigatorinstead/jira-issue-triage:investigate-and-refine <TICKET>chains investigator + refiner + prose-style and pauses onceAzure triage
/azure-issue-triage:setupruns and writes.claude/azure-issue-triage.config.json.mcp.jsonresolves the PAT via dotenvx and@azure-devops/mcpconnects torolaillc.mcp.jsonoverride takes precedence and the agent talks to the user's org/azure-issue-triage:investigate-and-refine <URL or ID>produces a clean investigation + refined title/descriptionAzure incident postmortem
/azure-incident-postmortem:setupruns and writes.claude/azure-incident-postmortem.config.jsonMCP namespacing
azure-devops-triageandazure-devops-postmortemare registered independentlyprose-styleskill resolves correctly under each plugin's namespace🤖 Generated with Claude Code