triage

Triage feature ideas into structured spec documents with codebase grounding.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/DiologIR/diolog-plugins --skill triage-diologir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/DiologIR/diolog-plugins/tree/main/plugins/feature-spec-pipeline/skills/triage
Command: npx skills add https://github.com/DiologIR/diolog-plugins --skill triage-diologir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of triaging feature ideas, transforming them into structured spec documents for implementation readiness assessment.

Core Features & Use Cases

  • Feature Triage: Triage feature ideas for implementation readiness.
  • Spec Document Creation: Automatically create spec documents with structured sections.
  • Codebase Grounding: Locates and maps references to the codebase.
  • Sentinel Review: Incorporates a review of product, UX, and regulatory gaps.
  • Assumptions and Questions: Handles assumptions and essential questions to ensure completeness.
  • Use Case: Ideal for teams managing a pipeline of feature ideas, enabling them to quickly evaluate and document feature readiness for further planning and development.

Quick Start

Triage the feature idea "Implement a new user profile feature" into a spec document using the /triage command.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automatically triage feature ideas for implementation readiness?

To triage feature ideas for implementation readiness, you can use a tool that integrates with your codebase to evaluate product, UX, and regulatory gaps, outputting a structured spec document with status and recommendations.

What is the best way to create structured spec documents from feature ideas?

The best way to create structured spec documents is by automating the triage process, which maps feature ideas to codebase references and handles assumptions and essential questions to ensure completeness.

Do I need codebase access to generate feature spec documents?

Yes, you need codebase access to generate feature spec documents, as grounding the review in the actual codebase is required to accurately map references and identify product, UX, and regulatory gaps.

How does codebase grounding improve feature readiness reviews?

Codebase grounding improves feature readiness reviews by locating and mapping references directly within the existing code, ensuring the resulting spec document accurately reflects implementation constraints and regulatory gaps.

Can I review UX and regulatory gaps when triaging product features?

Yes, you can review UX and regulatory gaps when triaging product features, as the triage process incorporates a sentinel review that evaluates these specific areas alongside product requirements to ensure full readiness.

What limitations exist when automating feature spec creation?

A limitation of automating feature spec creation is its strict dependency on codebase access for grounding; without the ability to map references to the actual code, the review for implementation readiness cannot function properly.