marketplace/bundles/pm-requirements/skills/ext-triage-reqs/SKILL.md
Triage extension for requirements findings during plan-finalize phase
npx skillsauth add cuioss/plan-marshall ext-triage-reqsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Provides decision-making knowledge for triaging requirements-related findings during the finalize phase.
This skill is a triage extension loaded by the plan-finalize workflow skill when processing requirements documentation findings. It provides domain-specific knowledge for deciding whether to fix, suppress, or accept findings.
Key Principle: This skill provides knowledge, not workflow control. The finalize skill owns the process.
Loaded via resolve-workflow-skill-extension --domain requirements --type triage during finalize phase when:
pm-documents:ref-asciidoc)| Document | Purpose | |----------|---------| | suppression.md | AsciiDoc comment syntax for suppression | | severity.md | Requirements-specific severity guidelines | | pr-comment-disposition.md | PR review comment disposition (FIX / REPLY-AND-RESOLVE / ESCALATE) for requirements |
Registered in marshal.json under the requirements domain:
"requirements": {
"workflow_skill_extensions": {
"triage": "pm-requirements:ext-triage-reqs"
}
}
| Finding Type | Syntax |
|--------------|--------|
| Document lint | Inline comment suppression (see pm-documents:ref-asciidoc for format-specific syntax) |
| Link validation | // skip-link-check comment |
| Structure issue | Document exception in requirements metadata |
| Severity | Default Action | |----------|----------------| | Structure error | Fix (requirements must be well-formed) | | Missing traceability | Fix or document exception | | Format inconsistency | Fix for consistency | | Style warning | Accept or fix |
pm-requirements:requirements-authoring - Requirements authoring standardsdevelopment
Domain-owned OpenRewrite log-line finding parser for the java-cui domain — parses the
development
Domain-owned OpenRewrite marker detection for the java-cui domain — scans Java/Kotlin sources for cui-rewrite TODO markers, categorizes them by recipe, and fails the gate on any detected marker
development
Operator control surface for the marshalld build server — enrol/drop a project in the machine-global registry (the opt-in enable signal and anti-laundering wall), manage the daemon lifecycle (start, stop, drain, status, install, upgrade) version-pinned to the verified bundle copy, and inspect the daemon's per-project interaction-audit log (read-only)
tools
The tiny build-consumption client for the marshalld build server — submit a build job, bounded long-poll for its result, ping the daemon identity, and preflight registry-plus-liveness in one call; consumption only, never provisioning or enrolment