$ loading_
Triages issues with label-driven state transitions and durable, resumable records.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "triage-workflow" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/triage-workflow/SKILL.md 2. Save it as ~/.claude/skills/triage-workflow/SKILL.md 3. Reload skills and tell me it's ready
Use triage-workflow to triage this GitHub issue: inspect existing labels, determine the current state, advance it to the next valid state, and generate a durable triage record with next-step recommendations.
Returns the updated triage state, required label changes, triage decision, and a resumable triage artifact.
Continue this work item from a previously saved triage record: restore the last state, verify current labels, and reassess with any new information before moving it to the correct state.
Provides restored context, an updated state assessment, label correction suggestions, and the continued triage result.
Run triage-workflow on this Azure DevOps work item: use its labels and content to determine the triage stage, perform a valid state transition, and produce an auditable triage artifact.
Produces a clear stage classification, transition rationale, missing-information notes, and a standardized triage record.
| State | Description |
|---|---|
unlabeled | New issue, never triaged |
needs-triage | Maintainer needs to evaluate |
needs-info | Waiting on reporter for more information |
ready-for-agent | Fully specified, ready for autonomous agent implementation |
ready-for-human | Requires human implementation |
wontfix | Will not be actioned |
Every issue should have exactly one state label. If conflicting state labels exist, flag the conflict and ask the maintainer which is correct.
| From | To | Who triggers | What happens |
|---|---|---|---|
unlabeled | needs-triage | Skill (first look) | Issue needs evaluation; apply label |
unlabeled | ready-for-agent | Maintainer | Well-specified, agent-suitable; write agent brief, apply label |
unlabeled | ready-for-human | Maintainer | Requires human; write summary, apply label |
unlabeled | wontfix | Maintainer | Out of scope or duplicate; close with comment |
needs-triage | needs-info | Maintainer | Underspecified; post triage notes with questions |
needs-triage | ready-for-agent | Maintainer | Clarification complete, agent-suitable; write agent brief |
needs-triage | ready-for-human | Maintainer | Clarification complete, needs human; write summary |
needs-triage | wontfix | Maintainer | Decided not to action; close with comment |
needs-info | needs-triage | Skill (detects reply) | Reporter replied; resurface for re-evaluation |
Only these transitions are valid. Flag unusual transitions.
Triage notes, agent briefs, summaries, comments, and any label-driven artifacts written to the board follow the Content Style rules in the work-item-creation skill: no emojis or decorative Unicode, no em-dash or hyphen as separator between concepts, never #<number> in free text (Azure DevOps auto-links it), no contrastive framing, direct active voice, no promotional language, short concrete prose.
When this skill writes any content to GitHub or Azure DevOps (state-change comments, agent briefs, info requests), apply those rules before sending.
State is managed via labels:
| Label | Color (hex) |
|---|---|
needs-triage | fbca04 |
needs-info | d93f0b |
ready-for-agent | 0e8a16 |
ready-for-human | 1d76db |
wontfix | e4e669 |
When transitioning: remove old state label, add new state label. Ensure the category label (bug or enhancement) is also present.
Map states to the process template's workflow states (per board-config). Use tags for supplementary classification (ready-for-agent, needs-info).
ready-for-agent)Post as a comment on the issue:
> This was generated by AI during triage.
## Agent Brief
**Objective**: [What needs to be built or fixed, in domain language]
**Acceptance criteria**:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
**Context**: [What the agent needs to know about the codebase area]
**Constraints**: [Any limits on the approach]
Durability rules apply: no file paths, no line numbers. Describe behavior and domain concepts.
needs-info)Post as a comment:
> This was generated by AI during triage.
## Triage Notes
**What we have established so far:**
- [Point 1]
- [Point 2]
**What we still need from you (@reporter):**
- [Specific, actionable question 1]
- [Specific, actionable question 2]
Include everything resolved during the clarification session. Questions must be specific, not vague ("please provide more info").
ready-for-human)Post as a comment with the same structure as agent brief, plus:
**Why this needs human implementation**: [Reason: judgment calls, external system access, design decisions, manual testing]
…
Standardize formatting and writing style for project Markdown documentation.
Systematically triage failures and fix broken builds or unexpected runtime issues.
Design and review software architecture diagrams for clearer, documentation-friendly visuals.
Create, switch, and verify Git branches before starting implementation work.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Clarify ambiguous plans and requirements through rigorous questioning and assumption testing.
Verify assignee, dependencies, priority, and capacity before starting a work item.
Triage microsoft/apm issues and produce one unified resolution comment.
Helps users triage workspace content items for next-step handling.
Create well-structured issues, stories, tasks, epics, and features on boards.
Triage support tickets by priority, ownership, and duplicate or known issue checks.
Triage inbox messages, route intents, track replies, and generate follow-up summaries.