triage-issue

Promotes a note-style issue into an implementation-ready specification anchored to existing code precedents.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill triage-issue-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/triage-issue
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill triage-issue-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlog issues often lack concrete, code-anchored acceptance criteria, making them impossible to implement or verify reliably. This Skill triages an existing tracker issue: it searches the repository for an existing code precedent, and either rewrites the issue body into a full specification (summary with boundaries, acceptance criteria, code references) or comments that a paired implementation session is needed first. ## Core Features & Use Cases - Precedent Detection: Searches the repository for existing code patterns that the issue's work can extend, using a shared precedent test. - Specification Rewriting: Rewrites the issue body into a structured format with boundaries, observable acceptance criteria, and references pointing to concrete code files rather than prose documents. - Guard Rails: Skips issues that are already code-anchored specifications or already in progress (checked acceptance criteria), never invents architecture, and never changes titles, labels, or checkbox states. - Use Case: After filing a vague issue with file-issue, run triage on issue #42 to determine whether it is ready for implementation; the Skill either upgrades it to an implementable specification or comments explaining what is missing. ## Quick Start Ask the assistant to triage issue number 42 and promote it to an implementation-ready specification if a code precedent exists.

Frequently Asked Questions about triage-issue

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

FAQPage Schema
How do I promote a vague issue into an implementable specification?

Run the triage-issue skill with the issue number, for example /sagittaras:triage-issue 42. It searches the repository for a code precedent and rewrites the issue body with boundaries, acceptance criteria, and code references if one exists.

What happens when no code precedent exists for an issue?

The skill leaves the issue body unchanged and posts a comment explaining what was searched for and not found. It recommends a paired implementation session first, since the skill never invents architecture on its own.

Does triage-issue work with both GitHub and Gitea?

Yes, it reads the Forge section of the project's CONTRIBUTING.md workflow configuration and uses the matching recipes. GitHub operations go through gh wrapper scripts, while Gitea uses MCP issue_read and issue_write tools.

When does triage-issue refuse to modify an issue?

It skips issues that already have filled acceptance criteria plus a code reference, issues with any checked checkbox indicating work in progress, closed issues, pull requests, and cases where the workflow configuration is missing.

Can triage-issue change issue titles, labels, or checkbox states?

No, it only rewrites the issue body. Titles and labels are left untouched, checkbox states are never toggled, and mismatches between title format and labels are only reported as a note in the output summary.