ext-triage-plugin

Triage marketplace plugin findings from pytest, plugin-doctor, markdownlint, and yamllint during plan-finalize.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill ext-triage-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ext-triage-plugin
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/pm-plugin-development/skills/ext-triage-plugin
Command: npx skills add https://github.com/cuioss/plan-marshall --skill ext-triage-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triages marketplace plugin findings during the plan-finalize phase to guide remediation and ensure consistent handling of quality issues across Python scripts, Markdown documentation, and YAML configurations.

Core Features & Use Cases

  • Structured triage workflow that classifies findings by source (pytest, plugin-doctor, markdownlint, yamllint) and assigns remediation actions.
  • Loadable as a plan-marshall workflow extension; integrates with extension contracts and registration metadata to apply standardized decisions during finalize.
  • Use Case: When tests fail or documentation has issues, the extension suggests fixes and prioritizes critical items.

Quick Start

Invoke the triage extension during the plan-finalize phase to categorize and prioritize plugin development findings.

Frequently Asked Questions about ext-triage-plugin

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

FAQPage Schema
How do I triage plugin findings from pytest and linting tools during plan-finalize?

To triage plugin findings during plan-finalize, load this extension into a plan-marshall workflow. It classifies issues from pytest, plugin-doctor, markdownlint, and yamllint, then assigns standardized remediation actions.

What is the best way to classify critical and warning findings in a plugin development workflow?

Classifying critical and warning findings in a plugin workflow is handled by applying standardized decision guidelines during the triage phase. This extension categorizes issues by severity to prioritize and guide remediation actions.

Can I use a triage extension to handle YAML configuration and Markdown documentation issues together?

Yes, you can handle YAML configuration and Markdown documentation issues together. This triage extension applies standardized decision guidelines to both file formats, alongside Python scripts, within the plugin development domain.

How do I register a plan-marshall workflow extension for plugin quality assurance?

To register a plan-marshall workflow extension for quality assurance, you use extension contracts and registration metadata. This ensures the triage standards are applied consistently during the plan-finalize phase.

Why do I need to triage quality issues before finalizing a plugin development plan?

You need to triage quality issues before finalizing a plan to ensure consistent handling of test, linting, and documentation errors. This process enforces triage standards and guides remediation decisions for critical findings.

What are the limitations of using a structured triage workflow for marketplace plugins?

The structured triage workflow is limited to the plugin development domain, specifically targeting Python scripts, Markdown docs, and YAML configurations. It enforces triage standards but relies on findings from predefined sources like pytest and yamllint.