Auto-offer /submit-for-review at end of /start

[sebastientaggart]

Replaces the closing prompt of /start (both Case A and Case B) so the user is invited to submit inline with a one-word reply instead of being told to manually run /submit-for-review.

New prompt (both cases):

"When you've verified locally, reply yes to submit, or say what to change."

• yes → invoke /submit-for-review inline
• anything else → treated as a change request, iterate, repeat the prompt

Notes on scope:

• The "scrap" branch was dropped. It had zero invocations across 100+ tickets and is better left to the user as an explicit make abandon call than nudged in a routine handoff prompt.
• Case A and Case B now share the same close-out, removing a long-standing asymmetry (Case B previously offered fewer options).
• Honest framing: this is a UX/consistency change, not an automation gain. The decision points haven't changed; the user just types one word instead of remembering a slash command. The real automation wins live in the sibling tickets Tier /submit-for-review outcomes so clean reviews auto-proceed #170 (review tiering) and Spawn linked follow-up tickets from informational review notes #171 (auto follow-ups).

Part of #167.

Closes #169

[sebastientaggart]

Review Summary

Verdict: APPROVE

Findings

• [NOTE] The new prompt drops the explicit make dev / "test locally" verb in favor of "verified locally" — phrasing the PR description acknowledges as a UX/consistency change. Source template skills/github-agile/start.md and all four generated adapters (.agents, .claude, .cursor, .gemini) are updated consistently and hashes are regenerated, so the sync invariant holds.
• [NOTE] Removing the "scrap" branch from the close-out prompt is intentional per the PR description (zero invocations across 100+ tickets); make abandon remains available as an explicit user action.