raisedadead/triage
plugins/dp-cab/skills/triage/SKILL.md
Use when the filing cabinet has accumulated items and needs cleanup — 'triage the backlog', 'clean up filed items', 'what can we close', 'prioritize the bugs'. Batch validation, consolidation, and promotion.
$ install --global
skillsauthnpx skillsauth add raisedadead/dotplugins triageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 10:33 AM57.8s2 files scanned
SKILL.md
- name:
- triage
- description:
- Use when the filing cabinet has accumulated items and needs cleanup — 'triage the backlog', 'clean up filed items', 'what can we close', 'prioritize the bugs'. Batch validation, consolidation, and promotion.
- user-invocable:
- true
- allowed-tools:
- Bash(bash -c *) Bash(printf *)
dp-cab:triage -- Filing Cabinet Triage
Read ${CLAUDE_SKILL_DIR}/references/triage-ceremony.md for full protocol details.
Pre-check
if ! command -v dp-engine >/dev/null 2>&1; then echo "NO_ENGINE"; exit 0; fi
if ! dp-engine status >/dev/null 2>&1; then echo "NO_DB"; exit 0; fi
echo "OK"
If NO_ENGINE: "dp-engine binary not found. Reinstall the dp-cab plugin." and STOP.
If NO_DB: "No tracker DB found." and STOP.
Discover Items (two sources)
Source 1: Cabinet children
cabinet=$(dp-engine query "label=dp-cab:cabinet AND type=epic AND (status=open OR status=deferred)" 2>/dev/null | jq -r ".[0].id // empty")
if [ -z "$cabinet" ]; then echo "NO_CABINET"; exit 0; fi
echo "CABINET=$cabinet"
dp-engine children-open "$cabinet" | jq -r ".[] | {id, title, status, priority}"
If NO_CABINET, report: "No FILING-CABINET epic found." and STOP.
Source 2: Cross-plugin side-quests
dp-engine query "label=dp-cab:filed AND status=open" 2>/dev/null | jq -r ".[] | {id, title, status, priority}"
Merge both sources (deduplicate by ID). Present a numbered inventory table.
If empty across both sources: "Nothing to triage." and STOP.
Phases
Walk through six phases in order: validate, consolidate, assess, promote, prioritize, summary. Follow the protocol in ${CLAUDE_SKILL_DIR}/references/triage-ceremony.md for each phase.
Ask: "Ready to begin validation?" before starting.
Delegation: Triager Agent
For tracker mutations and codebase verification, dispatch the triager agent instead of running commands in the main thread.
Main thread keeps:
- Presenting items to the user
- AskUserQuestion for per-item decisions (close? merge? promote?)
- Phase orchestration (validate → consolidate → assess → promote → prioritize → summary)
Triager agent gets dispatched for:
- Tracker close/merge/reparent/label operations
- Codebase grep for resolution evidence
- Ownership checks (dp-cto labels before mutating)
Dispatch via: Agent tool with subagent_type: "dp-cab:triager", include the issue ID(s) and requested action in the prompt. Parse the triager's receipt to confirm results before presenting to the user.
NEVER
- NEVER auto-close, auto-promote, or auto-merge without explicit user confirmation per item
- NEVER skip the validate phase -- always check for evidence of resolution
- NEVER skip the assess phase -- every surviving item gets a structured card with a verdict
- NEVER promote an item without a signed-off verdict from the user
- NEVER invoke planning skills -- triage only marks items ready
- NEVER modify the FILING-CABINET epic itself -- only its children
- NEVER invoke any non-
dp-enginetracker CLI -- always usedp-enginesubcommands - NEVER ask more than one decision question per message
Related Skills
raisedadead/self-develop
development
VerifiedTrustedCommunity
Use when the user shares a URL, names a resource from SOURCES.md, shares operational feedback, says 'adopt', 'learn from', 'what can we steal from', 'compare with', 'self-develop', or 'how do we get better'.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/setup
tools
VerifiedTrustedCommunity
Use when you need to set up or rebuild the dp-lsp Docker image after installing the plugin — 'set up LSP', 'build the image', 'install language servers'.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/tdd
development
VerifiedTrustedCommunity
Use when you want to write tests first, enforce test-driven development, or add test coverage — 'write tests for this', 'TDD this feature', 'add test coverage'. Strict RED-GREEN-REFACTOR discipline.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/spec
testing
VerifiedTrustedCommunity
Use when starting major work that needs formal design review — cross-team changes, architectural decisions, or complex features where requirements need discovery before implementation.
4SKILL.mdUpdated Apr 18, 2026