Can I customize the triage decision logic?

The skill follows established standards defined in severity.md and suppression.md to ensure consistent decision-making across the requirements domain.

When is this skill typically loaded?

It is loaded during the finalize phase specifically when issues like traceability gaps, link validation errors, or requirements structure inconsistencies are detected.

How does it handle AsciiDoc errors?

It offers specific guidelines and suppression syntaxes, such as '// asciidoc-lint-disable', to manage validation errors without breaking document standards.

What is the primary role of the Requirements Triage Extension?

It provides the specific knowledge required to decide how to handle findings—such as errors or gaps—found in requirements documentation during the finalization phase of a workflow.

Does this skill take control of the entire workflow?

No, this is a triage extension. It provides decision-making knowledge while the finalize skill (part of Plan Marshall) owns the actual process control.

Requirements Triage Extension

Name: Requirements Triage Extension
Author: cuioss

bycuioss

Content Management

Automates decision-making for resolving requirements documentation findings and AsciiDoc validation errors.

About

This skill acts as a specialized extension for the Plan Marshall orchestration layer, providing the domain-specific intelligence needed to triage requirements findings during the project finalization phase. It enables Claude to intelligently decide whether to fix, suppress, or accept issues related to AsciiDoc syntax, document structure, and traceability gaps. By applying standardized severity guidelines and suppression methods, it ensures that project documentation remains consistent, reliable, and compliant with organizational standards without manual intervention.

Key Features

Standardized suppression syntax for link checks and linting rules
Severity-based decision framework for requirements structure issues
Seamless integration with Plan Marshall's plan-finalize workflow
Detection and resolution guidelines for requirements traceability gaps
Intelligent triage for AsciiDoc validation and linting errors
0 GitHub stars

Use Cases

Automating the cleanup of documentation errors during the final stage of a development sprint
Enforcing consistent document structure across large-scale requirements repositories
Managing exceptions for legacy requirements or draft documentation during migration

About

Key Features

Standardized suppression syntax for link checks and linting rules
Severity-based decision framework for requirements structure issues
Seamless integration with Plan Marshall's plan-finalize workflow
Detection and resolution guidelines for requirements traceability gaps
Intelligent triage for AsciiDoc validation and linting errors
0 GitHub stars

Use Cases

Automating the cleanup of documentation errors during the final stage of a development sprint
Enforcing consistent document structure across large-scale requirements repositories
Managing exceptions for legacy requirements or draft documentation during migration