raisedadead/board
plugins/dp-cab/skills/board/SKILL.md
Use when you want to see project status, check what is in progress, view the backlog, or get a dashboard of current work — 'show me the board', 'what is open', 'sprint status'.
$ install --global
skillsauthnpx skillsauth add raisedadead/dotplugins boardInstall 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 AM42.4s4 files scanned
SKILL.md
- name:
- board
- description:
- Use when you want to see project status, check what is in progress, view the backlog, or get a dashboard of current work — 'show me the board', 'what is open', 'sprint status'.
- user-invocable:
- true
- allowed-tools:
- Bash(bash -c *) Bash(printf *)
dp-cab:board — Board Management
Current Stage
!dp-engine state 2>/dev/null || printf '{"stage":"idle"}'
Context Detection
Detect the current state to infer the appropriate mode:
-
Check for active sprint:
dp-engine query "label=dp-cab:sprint AND status=open" 2>/dev/null | jq -r ".[0].id // empty" -
Check for stale state (closeable epics, old loop files, stale labels):
ls .claude/ralph/*.md 2>/dev/null | wc -l
Route based on context:
| Condition | Action |
| ------------------------------------------- | ---------------------------------------------------------------- |
| Active sprint exists | Sprint view (review/progress) |
| No sprint, no stale state | Dashboard |
| Stale files detected | Suggest cleanup |
| Ambiguous or args non-empty (internal hint) | Use args as mode hint |
| Cannot determine | Present menu via AskUserQuestion: Dashboard / Sprint / Cleanup |
If the user wants Sprint, follow up: "Which sprint operation? plan / review / retro / close"
Then proceed to the corresponding mode below.
Pre-check
Verify the dp-engine binary is available:
command -v dp-engine
If dp-engine is not on $PATH, report: "dp-engine CLI not found. Install dp-engine prerequisites to use /dp-cab:board." and STOP.
Verify the tracker DB is initialized:
dp-engine status >/dev/null 2>&1
If status fails, report: "No tracker DB found. Run /dp-cto:plan or /dp-cto:spec to auto-initialize, or run dp-engine init manually." and STOP.
Mode: Dashboard
Read ${CLAUDE_SKILL_DIR}/references/dashboard.md and follow the dashboard protocol.
Mode: Sprint
Read ${CLAUDE_SKILL_DIR}/references/sprint.md and follow the protocol for the specified subcommand.
Mode: Cleanup
Read ${CLAUDE_SKILL_DIR}/references/clean.md and follow the cleanup protocol.
NEVER
- NEVER modify tracker state in dashboard mode — it is read-only
- NEVER create a sprint without user confirmation of theme and feature selection
- NEVER close a sprint with incomplete features without user confirmation
- NEVER run cleanup without showing what will be cleaned and getting user confirmation
- NEVER suggest actions in dashboard mode — present data only
- NEVER fabricate metrics — derive all data from
dp-engine queryresults
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