raisedadead
27 verified skills108 total stars
manage
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'.
testing4
challenge
Use when a draft spec is ready for adversarial review from multiple critical perspectives — requires completed draft phase.
tools4
adhoc-review
Use when you want a code review on recent changes, a specific file, or a pull request — 'review this', 'check my code', 'what did I miss'. Works in any project without setup.
development4
adhoc-debug
Use when you hit a bug, test failure, or unexpected behavior and want a structured investigation — 'debug this', 'why is this failing', 'find the root cause'.
development4
adhoc-research
Use when you need to look something up, validate a claim, check documentation, or gather evidence before making a decision — 'research this', 'is this true', 'find out how X works'.
testing4
adhoc-sweep
Use when you want to clean up drift, dead code, stale comments, or naming violations — 'sweep this', 'clean up', 'find dead code', 'check for drift'. Standalone entropy scan without an active epic.
development4
self-develop
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'.
development4
tdd
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.
development4
triage
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.
tools4
park
Use when you need to pause current work and come back later, or resume previously paused work — 'park this', 'pause the epic', 'pick up where I left off'.
tools4
file
Use when you have an idea, bug, or task to capture quickly — 'remember this', 'file this for later', 'note this down', 'add to backlog'. Quick-capture with context and priority.
tools4
debug
Use when encountering a bug, error, or failing test that needs structured investigation — 'this is broken', 'why does this fail', 'trace this error'. Enforces diagnosis before any fix attempt.
development4
review
Use when code changes are ready for quality review, after implementation completes, or before committing — 'review this', 'check quality', 'what needs fixing'.
development4
run
Use when a plan is ready and you want to execute it — 'run the plan', 'start building', 'dispatch the tasks'.
development4
adhoc-brainstorm
Use when you need to make a decision, compare options, or think through a list of items systematically — 'help me decide', 'weigh these options', 'walk me through the tradeoffs'.
testing4
draft
Use when research is complete and the PRD needs to be authored — requires completed research phase.
research4
setup
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'.
tools4
brainstorm
Use when discovery is complete and requirements need refinement with solution approaches explored — requires completed discover phase.
data-ai4
discover
Use when starting a new spec session to gather constraints, requirements, and boundaries — entry point for the spec pipeline.
devops4
evidence-protocol
Use when an implementation agent needs to verify claims are grounded in evidence, not generated from memory.
testing4
evidence-protocol
Use when an implementation agent needs to verify claims are grounded in evidence, not generated from memory.
testing4
board
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'.
testing4
handoff
Use when a spec is approved and needs decomposition into scoped implementation tasks — requires completed challenge phase.
tools4
plan
Use when you have clear requirements and want to go straight to implementation planning — task breakdown, dependency ordering, and agent-ready prompts. Use after /dp-cto:spec for specced work, or directly for well-scoped tasks.
development4
research
Use when you need to validate a technical decision, investigate prior art, check feasibility, or gather evidence — 'is this approach viable', 'what are the alternatives', 'find evidence for this'.
testing4
setup-engine
Use when dp-engine binary is missing or needs reinstallation -- called by plan skill on first use, not directly by user.
tools4
spec
Use when starting major work that needs formal design review — cross-team changes, architectural decisions, or complex features where requirements need discovery before implementation.
testing4