booley-ticket-createlisted

# Create Ticket All companion files sit in this skill's directory, alongside this file. **Schema:** `TICKET_TEMPLATE.md` — single source of truth for frontmatter fields and per-type body structure. Read it before writing a ticket. **Grilling guide:** `grilling.md` — read **only** in detailed-plan mode (Step 2c). Lightweight tickets never need it. **Usage:** ``` booley-ticket-create <fuzzy description> # human mode (default) booley-ticket-create --agent <structured input> # agent mode — no interaction ``` ## Output Boundary Ticket creation authors only the Ticket, Target definitions and unambiguously owned `tests.toml` tables approved at the Step 2f gate, and empty placeholder files for Scope paths marked `[new]`. A planned Target may be added to an existing Target-definition file, but existing Targets remain unchanged. The developer who runs the Ticket authors its implementation. A placeholder is a zero-byte file: do not put declarations, modules, packages, assertions, stimulus, functions, comments, or any other content in it. Leave existing RTL (including Verilog/SystemVerilog/VHDL), HDL testbenches, firmware, Python, scripts, constraints, generators, build hooks, and every other implementation or support-code file unchanged. If validation or enqueue would require code beyond an approved new Target definition, stop and report the blocker; creating that code is outside this skill. ## Step 1: Parse Input `--agent` in `$ARGUMENTS` → **agent mode** (Step 3).