to-ticket
Split approved product and architecture specifications into vertical implementation tickets and plans.
How do I install this agent skill?
npx skills add https://github.com/omegafrog/harness-codex --skill to-ticketIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill facilitates the management of technical specifications by splitting them into actionable implementation plans. It follows security best practices by requiring explicit human approval before modifying any files or external issue trackers and shows no signs of malicious behavior or vulnerabilities.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
to-ticket
What it does
to-ticket is the public entrypoint for turning Product Spec and Architecture Spec into vertical implementation slices. It recommends a clean split, waits for approval, and then prepares the Issue and plan structure needed for execution.
Flow
- Run
code-researchto get the current codebase baseline in compact form. - Split the spec into tracer-bullet or smart-zone vertical slices.
- Attach policy-based unit tests and
ui ~ entitye2e tests to each slice. - Define dependencies between slices.
- Present the split plan to the user and wait for approval before any mutation.
- After approval, create Issues and
plans.mdentries that match one-to-one. - Publish each Issue using tracker-specific labels or metadata.
- Apply
ready-for-agentonly when it can be handed toimplement. - Hand off the approved context to
implement.
Rules
- Do not mutate GitHub or local plan files before approval.
- Keep one Issue per split plan.
- Include policy-based unit tests and
ui ~ entitye2e tests in every plan slice. - Do not split only by layer.
- Apply labels or metadata at publish time, not during the planning-only pass.
- Use the current spec and codebase summary as the source of truth.
Pulled out on purpose
to-ticket keeps the public surface small and pushes the actual splitting rules into the internal skill.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/omegafrog/harness-codex/to-ticket">View to-ticket on skillZs</a>