How does it handle missing or ambiguous information?

It uses an interactive questioning tool to ask the user for clarification on blockers and scope. Any remaining unanswered questions are then documented in a formal triage report.

Where does the skill store its analysis reports?

Reports are automatically saved as Markdown files in the ./.aiwork/triage/ directory within your project, using slugified titles for easy organization.

When should I trigger the Triage skill?

Trigger it whenever you receive a new requirement or bug report by mentioning keywords like 'triage', 'review this spec', or 'is this requirement complete'.

Can this skill read my project's internal documentation?

Yes, it specifically searches through directories like docs/, wiki/, and files such as README.md or API specs to find implicit requirements and business rules.

What is the primary purpose of the Triage skill?

The Triage skill is designed to evaluate issues, specs, or requirements for completeness by comparing them against your existing codebase and documentation to find gaps before work begins.

Triage & Requirements Analysis

Name: Triage & Requirements Analysis
Author: lttr

bylttr

•

협업 도구

Analyzes issues and specifications against your codebase to identify missing requirements and surface clarifying questions before implementation.

소개

The Triage skill streamlines the pre-development phase by performing a deep analysis of new tickets, bug reports, and feature specifications. By cross-referencing input against existing codebase patterns and documentation, it identifies implicit constraints, technical dependencies, and potential edge cases that might otherwise be overlooked. This skill automates the discovery of missing information through interactive questioning, ensuring that tasks are fully defined and ready for implementation with a clear scope and minimal ambiguity.

주요 기능

Identification of implicit business rules and architectural constraints
1 GitHub stars
Interactive questioning to resolve blockers and scope gaps
Standardized triage reports saved directly to your project directory
Deep exploration of local documentation and codebase context
Automated assessment of requirement completeness and clarity

사용 사례

Assessing if a new GitHub issue or Jira ticket has enough detail to start development
Reviewing complex feature specifications to ensure alignment with existing architecture
Surfacing hidden dependencies and edge cases for a bug report before writing a fix

소개

주요 기능

Identification of implicit business rules and architectural constraints
1 GitHub stars
Interactive questioning to resolve blockers and scope gaps
Standardized triage reports saved directly to your project directory
Deep exploration of local documentation and codebase context
Automated assessment of requirement completeness and clarity

사용 사례

Assessing if a new GitHub issue or Jira ticket has enough detail to start development
Reviewing complex feature specifications to ensure alignment with existing architecture
Surfacing hidden dependencies and edge cases for a bug report before writing a fix