denerose/vom-new
.cursor/skills/vom-new/SKILL.md
Guide for creating a new VOM ticket using the vom CLI so tickets are good-quality and workflow-aligned.
tools
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add denerose/VeganMealPlanner vom-newInstall 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:26 AM212.7s1 file scanned
SKILL.md
- name:
- vom-new
- description:
- Guide for creating a new VOM ticket using the vom CLI so tickets are good-quality and workflow-aligned.
VOM New Ticket
When the user asks to create a new ticket (or uses /vom-new), follow these steps so the new ticket is high-quality and fits the project's VOM workflow.
1. Align with the Workflow
If you are not already familiar with this project's VOM workflow, run:
vom --agents-help
Use that output to align with: claim → guidance → show → work → next, single-step per state, and acceptance criteria. New tickets should fit that workflow.
2. Good-Quality Tickets (This Project)
Title: Short, imperative, scoped to one workflow step or deliverable (e.g. "add X", "fix Y when Z", "document W").
Description: When useful, 1–3 sentences for context, constraint, or outcome so triage and planning have enough to set type, priority, and acceptance criteria. Use vom new "<title>" "<description>" or --file path for longer text.
Type and priority: Use vom new -t <type> -p <priority> "title" when obvious (e.g. -t bug -p critical for a critical bug); otherwise leave default and let triage set them.
Workflow fit: Tickets should be small enough for the single-step agent workflow (one state transition per agent run). If the user's request is large, suggest splitting into multiple tickets or a single ticket that will be broken down in planning—do not create one oversized ticket.
3. Create the Ticket
Run:
vom new "<title>"
Add optional description, type, or priority as above. For large or vague requests, suggest splitting or a planning breakdown before running vom new.
Examples:
vom new "add search to vom list"
vom new "fix login when session expired" "Users get 500 after session timeout; should redirect to login."
vom new -t bug -p critical "crash on empty input"
4. After Creation
Confirm the created ticket ID from the command output, then suggest the next step:
- Example: "Created TKT-006. Run
vom claim TKT-006when ready to work it."
Run vom --agents-help first if unsure about the workflow. This keeps new tickets consistent with claim → guidance → show → work → next and good-quality title/description/type/priority.
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