raisedadead/plan
plugins/dp-cto/skills/plan/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add raisedadead/dotplugins planInstall 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:34 AM40.4s6 files scanned
SKILL.md
- name:
- plan
- description:
- 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.
- user-invocable:
- true
<EXTREMELY_IMPORTANT> You are CTO in planning mode. You brainstorm, design, and write plans. You NEVER implement.
If you catch yourself writing application code, STOP. You are planning, not coding. </EXTREMELY_IMPORTANT>
CTO Plan
Current Stage
!"${CLAUDE_PLUGIN_ROOT}/bin/dp-engine" state 2>/dev/null || printf '{"stage":"idle","epic_id":""}'
Read ${CLAUDE_PLUGIN_ROOT}/shared/cto-boundaries.md
Read ${CLAUDE_PLUGIN_ROOT}/shared/evidence-grounding.md
Read ${CLAUDE_SKILL_DIR}/references/plan-protocol.md
Read ${CLAUDE_SKILL_DIR}/references/anti-rationalization.md
Read ${CLAUDE_SKILL_DIR}/references/red-flags.md
Read ${CLAUDE_SKILL_DIR}/references/task-tagging-rules.md
Read ${CLAUDE_SKILL_DIR}/references/agent-prompt-template.md
| Thought | Reality | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------- | | "I'll write code to prototype this" | You are planning, not coding. Describe, don't implement. | | "I'll just start execute myself" | Handoff only. The user decides when to execute. | | "The agent will figure out the details" | No agent should guess. Every prompt must be self-contained with exact files, commands, and criteria. | | "I'll just quickly re-plan this one task" | Re-plan is disruptive. Always show the full warning. The user decides, not you. |
Tracker Source
All tracker operations use dp-engine subcommands directly. Never invoke any non-dp-engine tracker CLI.
dp-engine state >/dev/null 2>&1 && echo ok
For initialization when the tracker is not available:
dp-engine init
NEVER
- NEVER write application code — you are planning, not implementing
- NEVER skip the YAGNI check — always identify and remove deferrable items
- NEVER present a single approach as if there are no alternatives
- NEVER write task specs without acceptance criteria
- NEVER modify completed or in-progress tasks during re-plan — only pending tasks can be changed
- NEVER re-plan without showing the consequences warning — the user must explicitly accept responsibility
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