raisedadead/manage
plugins/dp-cab/skills/manage/SKILL.md
Use when you need to close, reopen, defer, or verify a filed issue — 'close this issue', 'reopen that bug', 'defer this to later', 'is this actually done'.
$ install --global
skillsauthnpx skillsauth add raisedadead/dotplugins manageInstall 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:
- manage
- description:
- Use when you need to close, reopen, defer, or verify a filed issue — 'close this issue', 'reopen that bug', 'defer this to later', 'is this actually done'.
- user-invocable:
- true
- allowed-tools:
- Bash(bash -c *) Bash(printf *)
dp-cab:manage -- Issue Lifecycle Management
Current Stage
!dp-engine state 2>/dev/null || printf '{"stage":"idle"}'
Read ${CLAUDE_SKILL_DIR}/references/manage-protocol.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 CLI not found. Install dp-engine prerequisites to use /dp-cab:manage." and STOP.
If NO_DB: "No tracker DB found." and STOP.
Parse Arguments
If no action is provided, present this menu:
What would you like to do?
- Close an issue
- Reopen an issue
- Defer an issue
- Verify acceptance criteria
- Audit for ghost-closes
Wait for the user to choose before proceeding.
Ownership Check
Before any mutation (close, reopen, defer), read the target issue's labels:
dp-engine show "[ISSUE_ID]"
Check the labels in the output:
- If
dp-cto:running,dp-cto:planning, ordp-cto:reviewing: show "This item has {label} -- it may be actively worked. Continue?" and wait for confirmation. - If
dp-cto:agent-spawning: show "Agent dispatched on this item. Continue?" and wait for confirmation. - If no dp-cto labels: proceed normally.
Dispatch
For close as completed: dispatch the triager agent to verify acceptance criteria against the codebase before closing. Do not close without verified criteria.
For all other actions (close with other reasons, reopen, defer, audit): execute directly using dp-engine subcommands per the protocol in references/manage-protocol.md.
Post-action
Report the result to the user:
{issue-id}: {action} -- {result}
Reason: {reason}
Evidence: {file:line or dp-engine show output}
NEVER
- NEVER close as
completedwithout acceptance criteria verification - NEVER mutate an issue without the ownership check
- NEVER auto-select from the menu -- wait for user choice
- NEVER modify code files -- this skill manages tracker state only
- NEVER invoke any non-
dp-enginetracker CLI -- always usedp-enginesubcommands
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