Write Ticket

Develop the final ticket in the same chat as the research and decisions. User start only; /task reads tickets (ticket context). This skill never implements the ticket.

Read when

• Preparing a touched user flow? Open user-experience.md during investigation and carry the result into the Plan's conditional UX/UI section. Backend-only work skips this.
• About to analyze or draft? Open code-quality.md, code-structure.md, and doctrine.md. Skip them and the ticket plans a shape the rules reject.
• About to grill or draft for a Feature? Open strong-foundation.md. Skip it and the Plan has no seams where a new variant plugs in.
• About to ask? Open Asking the user and the relevant reference.md guidance. Skip them and you ask for facts the repo or tracker already has.
• About to draft? Open Plain language. Skip it and the ticket needs this pack to make sense.
• About to draft or write? Open the Plan body, fresh-executor handoff, and final-version description. Skip them and the ticket needs the old chat to make sense.

Process