assess-ticket: Prompt for next steps after non-baseline verdicts

[williamthorsen]

assess-ticket: Prompt for next steps after non-baseline verdicts

Problem

After running assess-ticket, the response to non-baseline verdicts is highly predictable — drift triggers a ticket update, completion triggers a close with comment, etc. — but the user must manually formulate and request these actions every time.

Context

The skill currently ends at output (step 3) with the principle "No action, just assessment." The existing _data/next-steps-after-plan.md and _data/next-steps-after-review.md establish a pattern for post-skill action prompts, but those are shared reference documents used by multiple skills. This file is skill-local because only assess-ticket uses it.

Branch 372 (pending merge) adds a "skip complexity when progress is complete" optimization that changes step 2 and step 3 text. This work builds on the post-372 state.

Solution

Add a new reference document next-steps-after-assessment.md inside the assess-ticket/ skill directory containing the verdict-to-actions mapping and interaction protocol. Modify SKILL.md to add a step 4 that references the new document, update the "no action" principle, and update the skill description.

Verdict-to-actions mapping

Verdict	Actions
Drift: partial	Update ticket to align with current codebase state
Drift: severe	(a) Update ticket to align with current codebase state (b) Close as outdated
Relevance: uncertain	Add comment noting ambiguous relevance for human triage
Relevance: superseded	Close with comment explaining what superseded it
Progress: partial	(a) Close ticket and create a new ticket scoped to remaining work (b) Update ticket to reflect completed items and remaining work
Progress: complete	Close with comment summarizing completed work and referencing changes

Complexity verdicts are purely informational and never trigger a prompt.

When multiple dimensions trigger actions, they are combined into a single numbered list, deduplicated, and ordered by dimension (drift → relevance → progress). "No action" is always the last option.

Acceptance criteria

• New file assess-ticket/next-steps-after-assessment.md contains the verdict-to-actions mapping, baseline definition, and interaction protocol
• SKILL.md has a new step 4 ("Next steps") referencing the new document
• The "No action, just assessment" principle is replaced with "Assessment first, action on request"
• The skill description in frontmatter reflects the new capability
• Non-baseline verdicts in any mode (all or single) produce a numbered action prompt
• All-baseline verdicts produce no prompt
• Actions describe intent only — no platform-specific commands