Problem
design-and-plan emits no lifecycle events. A session running it — typically a long, interactive one — narrates none of its work to the event log: no skill start or completion, no input-wait signals while design questions sit unanswered, no artifact.written for the ticket and plan it saves. Once #1005 lands, session hooks make such sessions visible with turn-level state, but what the session is doing stays invisible.
Context
Acceptance criteria
Must have
Problem
design-and-planemits no lifecycle events. A session running it — typically a long, interactive one — narrates none of its work to the event log: no skill start or completion, no input-wait signals while design questions sit unanswered, noartifact.writtenfor the ticket and plan it saves. Once #1005 lands, session hooks make such sessions visible with turn-level state, but what the session is doing stays invisible.Context
review-branch,respond-to-review, andcreate-prat their lifecycle boundaries via the_partials/lifecycle-events.mdpartial and the emit-event helper;design-and-planfollows the same pattern.Acceptance criteria
Must have
design-and-planemits work-narration events at its lifecycle boundaries per thelifecycle-eventsconventions: skill start and completion, input waits, andartifact.writtenfor the saved ticket and plan artifacts.