ticket-workflow
Ticket Workflow
Scope
Coordinate one standalone ticket through requirements intake, implementation transition, and final PR readiness. ticket-requirements-gathering owns Setup through Plan approval; invoke it from intake and consume its approved handoff. Detailed implementation, review, QA, UI verification, and fix-loop mechanics belong to the implementation-workflow skill.
Do not use this workflow for a related batch of tickets. If a fresh approved requirements handoff and execution mode are already established, the ticket is already In Progress, and the request is only to execute, review, verify, and open a PR, invoke implementation-workflow directly. This shortcut is not available for a ticket marked prototype-backed.
Mandatory lifecycle:
Setup -> Brainstorm -> Spec/design approval -> Plan approval -> Implementation -> Parity step (prototype-backed tickets) -> PR readiness
Approval is artifact-specific. A user can approve only an artifact they have seen. Agreement with decisions, assumptions, recommendations, investigation progress, or "good to go" does not approve an unwritten spec/design or implementation plan.
Session Title
When a chat session starts with this skill, name that session after the ticket: use the user story id and title, for example ABC-123 Add password reset. If the session started before the ticket was identified, set the title as soon as intake resolves the id and title. If the session title cannot be set, say so and continue.