forge-triagelisted

Triage and validate Forge project management issues before development begins. Use this skill whenever issues need to be reviewed for completeness, classified by complexity, or assigned category/priority. Triggers on: /forge-triage, triaging issues, validating issue quality, classifying issue complexity, setting issue priority, reviewing new issues, checking if issues are actionable. Also use when the pipeline needs to move an issue from open to confirmed status. Even if the user just says 'triage this' or 'check if this issue is ready', use this skill.
SidCorp-co/forge · ★ 4 · AI & Automation · score 73

Install: claude install-skill SidCorp-co/forge

# Forge Triage Triage gates the pipeline — it catches incomplete issues before they waste expensive planning and coding cycles. An issue that bounces back with questions burns an entire plan-code-review round trip. Operate purely on issue data via MCP tools. Do not read the codebase — triage should be fast and cheap. Codebase exploration happens in `forge-plan`. ## Usage ``` /forge-triage <documentId> /forge-triage <documentId1> <documentId2> ``` ## Tools - **forge_issues** — get/update issues - **forge_comments** — list/create comments ## Workflow ### Step 1: Fetch Issue Data Fetch the issue and its comments in parallel: ``` forge_issues → get → { documentId: "<id>" } forge_comments → list → { filters: { issue: "<documentId>" } } ``` Review all available fields: title, description, acceptanceCriteria, aiAcceptanceCriteria, suggestedSolution, aiSuggestedSolution, plan, category, priority, status, comments. For multiple issues, triage each independently — separate assessments, separate comments. ### Step 2: Evaluate Completeness Read `references/triage-criteria.md` for the full criteria. The core question: **can a developer understand what to change and what the result should be?** If the issue is actionable → proceed to Step 3. If the issue is incomplete → set `needs_info` and stop: ``` forge_issues → update → { documentId: "<id>", data: { status: "needs_info" } } forge_comments → create → { data: { body: "<specific questions>", issue: "<documentId>", author: