Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By incubyte
Triage issues end-to-end on Azure DevOps and Jira across all archetypes (Bug, Incident, Story, Feature, Task, Spike) with a single diff-and-confirm gate that investigates, refines, assigns, sets metadata, links related work, and posts Slack/Teams summaries.
npx claudepluginhub incubyte/ai-pluginsLightweight triage — investigate and refine the title/description only. No assignment, no transition, no severity write, no escalation. Useful when you want to clean up a ticket without committing to the full triage cycle.
Full end-to-end issue triage. Investigates, refines title/description, sets severity/sprint, links related work, applies the triaged label, and posts a summary. All writes pass through a single diff-and-confirm gate.
Restructures a poorly written tracker issue into a clear, self-contained document a stranger can open cold and act on. Works on any archetype (Bug, Incident, Story, Feature, Task, Spike) and any supported tracker (Azure DevOps, Jira). Returns the refined title and markdown body; the caller owns the write (issuekit:tracker-adapter projects markdown to the vendor's format).
Investigates a non-bug issue (Story, Feature, Task, Spike) on any supported tracker (Azure DevOps, Jira) by reading the issue and linked design or product docs, searching chat (Slack/Teams) and docs (Confluence/Wiki) for prior decisions, and producing an evidence-tagged orientation report. Use when a developer is about to pick up a Story, Feature, Task, or Spike and wants context before starting work. For Bug/Incident, use issuekit:issue-investigator instead.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Shared adapter layer for issue-tracker plugins. Auto-detects the active MCP (Azure DevOps, Jira), exposes an abstract verb surface (getIssue, addComment, transition, linkIssue, ...), converts markdown bodies to the target format (HTML for Azure DevOps, ADF/markdown for Jira), and reads policy from .claude/tracker-policy.json. No MCP bundled, no agent, no slash command. Required by incident-postmortem and issue-triage.
Comprehensive Jira integration with auto-detection of issue keys
Complete JIRA automation suite with 14 specialized skills - issue management, agile workflows, time tracking, service management, bulk operations, and more
Smart task routing: classifies specs and routes to feature-dev or subagent-driven-dev
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Learn any technology by building real projects. Claude guides you step-by-step — you write every line of code yourself.
End-to-end product discovery flow that produces a structured PRD.
End-to-end incident postmortem generator. Paste an incident issue URL (Azure DevOps or Jira) and the agent gathers evidence from chat (Slack/Teams), the tracker (related issues, history), Datadog logs, and merged pull requests; reconstructs a chronological timeline with evidence tags; and writes a Google-SRE-style blameless postmortem (summary, impact, timeline, root cause, contributing factors, what went well/wrong, action items, lessons learned). Tracker-agnostic via issuekit. Bundles incident-timeline-builder and postmortem-writer skills.
Shared adapter layer for issue-tracker plugins. Auto-detects the active MCP (Azure DevOps, Jira), exposes an abstract verb surface (getIssue, addComment, transition, linkIssue, ...), converts markdown bodies to the target format (HTML for Azure DevOps, ADF/markdown for Jira), and reads policy from .claude/tracker-policy.json. No MCP bundled, no agent, no slash command. Required by incident-postmortem and issue-triage.
Bee — a spec-driven TDD workflow navigator for AI-assisted development. Guides developers through the right level of process: triage, spec, architecture, TDD planning, execution, verification, and review.
A collection of Claude Code plugins by Incubyte.
Spec-driven development that scales process to match the task. Triages by size and risk, then navigates you through the right workflow: triage, context gathering, spec, architecture, code, test, verify, review.
@bee inline annotationsEntry point: /bee:sdd
Learn any technology by building real projects. Claude guides you step-by-step — you write every line of code yourself.
Entry point: /learn:start
Builds a compounding wiki from raw documents. Drop articles into clippings/, ingest them into an Obsidian-compatible wiki with cross-references, then query your knowledge base with synthesized answers and citations.
[[wikilinks]] and YAML frontmatterEntry point: /second-brain:ingest
Take a raw product idea through ten guided phases and walk away with a structured PRD. Pushes back on vague metrics, refuses to write PRDs for ideas that should die.
discovery-state.mdEntry point: /discovery:start
Auto-detects the active issue-tracker MCP (Azure DevOps, Jira) and exposes an abstract verb surface (getIssue, addComment, transition, linkIssue, ...). Declared as a dependency by incident-postmortem and issue-triage; Claude Code auto-installs it when you install either verb-plugin. Ships no MCP, no agent, no slash command — it's a library.
.claude/tracker-policy.json; lazy-prompts for missing keys and offers to persist the answerEntry point: pulled in transitively by the verb-plugins; no direct user invocation.
Paste an incident URL (Azure DevOps or Jira) and the agent gathers evidence from chat (Slack/Teams), the tracker, Datadog logs, and merged pull requests; reconstructs a chronological timeline with evidence tags; pauses for review; then writes a Google-SRE-style blameless postmortem.
incident-timeline-builder, postmortem-writer/incident-postmortem:run <URL or ID>Auto-installs issuekit.
Entry point: /incident-postmortem:run <URL or ID>
Paste any issue URL (Azure DevOps or Jira; Bug, Incident, Story, Feature, Task, or Spike) and the agent triages it end-to-end: assigns to you, transitions to investigating, runs the matching investigation skill, refines title and description, posts an assessment comment, sets severity + due date or sprint + story points, links related work, applies the triaged label, and posts a summary to the configured chat channel.
issue-refiner, requirements-investigator (uses issuekit:issue-investigator for Bug/Incident)/issue-triage:run <URL or ID> — full workflow/issue-triage:investigate-and-refine <URL or ID> — lightweight subset (no severity, transitions, sprints, comments, labels, or escalation)Auto-installs issuekit.
Entry point: /issue-triage:run <URL or ID>
Add the marketplace once, then install the plugins you want:
/plugin marketplace add incubyte/ai-plugins
/plugin install bee@incubyte-plugins
/plugin install learn@incubyte-plugins
/plugin install discovery@incubyte-plugins
/plugin install incident-postmortem@incubyte-plugins
/plugin install issue-triage@incubyte-plugins