denerose/vom-open-plan
.cursor/skills/vom-open-plan/SKILL.md
Open the implementation plan file for a VOM ticket. Ticket ID can come from the user's request or from current context (e.g. open file under .vom/tickets/, conversation). Use when the user asks to open the implementation plan, when a ticket is in or transitions to plan-needs-review, or when viewing the plan for TKT-XXX.
tools
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add denerose/VeganMealPlanner vom-open-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 17, 2026, 6:28 AM312.0s1 file scanned
SKILL.md
- name:
- vom-open-plan
- description:
- Open the implementation plan file for a VOM ticket. Ticket ID can come from the user's request or from current context (e.g. open file under .vom/tickets/, conversation). Use when the user asks to open the implementation plan, when a ticket is in or transitions to plan-needs-review, or when viewing the plan for TKT-XXX.
VOM Open Plan
When asked to open the implementation plan for a VOM ticket (e.g. "open plan for TKT-017" or "open the plan" when a ticket is already in context):
-
Determine the ticket ID. If the user's request contains a ticket ID (e.g. "open plan for TKT-017", "17", "017"), parse it and normalize to full form
TKT-XXX(e.g. 17 → TKT-017). If the request does not contain a ticket ID, derive it from current context: (a) open files whose path is under.vom/tickets/(e.g..vom/tickets/TKT-017/ticket.mdor.vom/tickets/TKT-017/plans/implementation.md→ use that ticket id); (b) or the ticket currently under discussion in the conversation. If no ticket can be determined from request or context, ask the user which ticket and stop. -
Open the plan file using the Read tool:
.vom/tickets/<ticket-id>/plans/implementation.md(path from workspace root). -
If the file does not exist, tell the user that this ticket has no implementation plan yet (not all tickets have plans).
Related Skills
denerose/vom
testing
VerifiedTrustedCommunity
Guide for continuing work on a VOM ticket - reminds agents to claim and check guidance before starting.
SKILL.mdUpdated Apr 17, 2026
denerose/vom-tidy
data-ai
VerifiedTrustedCommunity
Move VOM tickets with state done or deleted into tickets/done or tickets/deleted to keep the main list tidy.
SKILL.mdUpdated Apr 17, 2026
denerose/vom-self-review
testing
VerifiedTrustedCommunity
Review recent work for friction and pain points. Create or update tickets for issues that made the agent's job harder. Focus on project-specific improvements only.
SKILL.mdUpdated Apr 17, 2026
denerose/vom-plan-review
tools
VerifiedTrustedCommunity
Reviews, amends, and improves a VOM implementation plan for a ticket in plan-needs-review using only the vom CLI for claims, guidance, comments, and state transitions; edits plan markdown under plans/ only. Use when the user wants a plan approved (moved to plan-approved), wants plan-needs-review handled end-to-end, or invokes plan review with extra notes or constraints in the prompt.
SKILL.mdUpdated Apr 17, 2026