skills.rest
ourchitecture
ourchitectureOFFICIAL
Explore all skills by this author →
WebsiteGitHub

triage-managed-work

Identify and triage branches, pull requests, and issues from maintainers or agents.

1|Updated Mar 12, 2026
Search Tags:#automation#workflow#github#issues#branches#triage#pull-requests
One-click install
npx skills add https://github.com/ourchitecture/idp --skill triage-managed-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-managed-work
Source: https://github.com/ourchitecture/idp/tree/main/.agents/skills/triage-managed-work
Command: npx skills add https://github.com/ourchitecture/idp --skill triage-managed-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps managed work visible by automatically identifying branches, pull requests, and issues created by maintainers or agents that need attention, explaining why each item requires action and recommending a concrete next step. This skill is designed to provide a triage dashboard of managed work items across the repository to prevent stalled work and miscommunication.

Core Features & Use Cases

  • Identifies maintainer or agent authors and filters items accordingly.
  • Aggregates active branches, PRs, and issues for focused triage.
  • Produces a structured triage report that surfaces reasons, severity, and next steps.
  • Supports optional reporting to a specific issue and returning a machine-readable output for automation.

Quick Start

Run triage-managed-work to generate a triage report of managed branches, PRs, and issues.

Frequently Asked Questions about triage-managed-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage stale GitHub branches and pull requests created by multiple maintainers?▼

You can run automated triage for managed work to filter GitHub branches, pull requests, and issues by maintainer or agent authors, applying stale_days rules to surface items needing attention with actionable recommendations.

What is the best way to automate GitHub issue triage across repositories with multiple agents?▼

Automated triage for managed work aggregates active GitHub issues across repositories, filtering by agent authors and applying base_branch rules to output a structured report with reasons, severity, and recommended next steps.

Can I generate a structured triage report for GitHub pull requests that need attention?▼

Yes, automated triage for managed work lists active GitHub pull requests, filters by maintainer or agent authors, and outputs a structured report detailing reasons, severity, and concrete next steps for items requiring action.

Does this triage workflow require the GitHub API or MCP tools to list active issues and branches?▼

Yes, automated triage for managed work relies on MCP tools or the GitHub API to list active items, filter by maintainer or agent authors, and apply stale_days and base_branch rules for triage reporting.

Can I post the GitHub triage report to a specific issue and return machine-readable output for automation?▼

Yes, automated triage for managed work supports optional reporting to a specific GitHub issue and returns machine-readable output, enabling continuous automation for managed work items across repositories.

Related Skills

Explore More Software Engineering Skills→
dr-codedr-code

github-automation

Automate GitHub issues, pull requests, branches, CI/CD, and deployments via Rube MCP.

Community
Advanced
aronpcaronpc
1

issues

Analyze GitHub issues to classify categories, detect duplicates and spam, and output structured priorities.

Community
Advanced
chf3198chf3198

github-review-merge-admin

Validate GitHub pull request approvals, status checks, and merge readiness.

Community
Intermediate
jonaseck2jonaseck2
2

oss-stale

Closes GitHub issues and pull requests inactive for 60+ days.

Community
Intermediate