contribution-triage

name	contribution-triage
description	Triage open-source issues and pull requests by validity, reproduction, scope, project fit, duplication, risk, ownership, and next action while preserving contributor context.

Contribution Triage

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using issue/PR body, repository state, roadmap/governance, tests, labels, and prior discussions. Do not fill material gaps with assumptions when they can change the result.
3. Normalize request, reproduce/inspect evidence, identify duplicates and affected surface, classify decision needed, request only necessary information, and assign clear state.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

Every item has an explicit next action or closure rationale and contributors are not left in ambiguous limbo.