issue-create: default to collaborative open-questions pass; drop post-create issue-work handoff

[SnowboardTechie]

Problem / Motivation

Two friction points in the current /issue-create flow, both surfaced while filing #69:

1. Open questions sit in the draft until the user explicitly nudges. Stage 3.3 shows the draft and accepts conversational edits, but it doesn't proactively try to close out the "Open questions" section. The pattern that worked well in Skill: /external-source-review — track pi-mono, PAI, … for primitives to absorb #69 — state a lean per question, ask user to confirm/override, commit reasonable defaults, re-render — only happened because I asked. Open questions are friction points that cost more to resolve later than to ask now while context is hot. Better-captured issues at create time make /issue-work significantly easier downstream.

2. The post-create "Start working on this now?" handoff is always declined. I always spin up a fresh-context agent for /issue-work. The prompt at Stage 4.6 is dead weight in my flow.

Proposed behavior

Collaborative open-questions pass

After the draft is rendered (Stage 3.2) and before the approval gate (Stage 3.3), if the draft contains an Open questions section with one or more items, the skill defaults to a collaborative resolution pass:

• Announce the pass: "Draft has N open questions. Want to close them out before posting? [yes / post as-is / skip]"
• On yes (default): for each question, state the skill's lean (if it has one — derived from the conversation context or stated as "no lean"), then ask the user to confirm, override, or defer. Commit reasonable defaults on items the user doesn't explicitly address.
• After the pass, re-render with resolved leans baked into the appropriate sections (Scope / Implementation hints / Acceptance criteria) and the Open questions section trimmed to whatever genuinely remains open.
• On post as-is or skip: leave the section untouched and continue to the existing approval gate.

The same pass also applies to template-derived drafts when the template includes an "Open questions" or equivalent free-form open-ended field.

Drop the issue-work handoff

Remove Stage 4.6's "Start working on this now?" prompt and the auto-invocation of /issue-work. The completion report still shows URL + metadata + archive path. The "Pairs with issue-work" header line stays (the relationship is still true), but the auto-handoff goes away — fresh-context agents are the right shape for implementation work.

Scope

In scope

• New Stage 3.x step (between draft render and approval gate) for the collaborative open-questions pass
• Skill prompt language for stating leans + capturing user response per question
• Re-render flow that incorporates resolved questions into the right sections
• Removal of the post-create issue-work handoff prompt at Stage 4.6
• Edge-case behavior: zero open questions → skip the pass silently

Out of scope

• Detecting open-shaped content outside an explicit "Open questions" section (e.g., "TBD" inline) — keep the trigger explicit for v1
• Persisting unresolved questions as follow-up sub-issues (separate idea)
• Changing how Stage 2's four open-ended areas work — those already happen pre-draft

Implementation hints

• The pattern that worked in Skill: /external-source-review — track pi-mono, PAI, … for primitives to absorb #69: I stated 4 leans, Bryan answered "a" (= option a for question 1), I committed reasonable defaults on 2/3/4, re-rendered with the Open Questions section dropped entirely. This is the shape to script.
• Where the lean comes from: prefer the skill's own assessment from the conversation context. When there's no clear lean, say so ("no lean — your call") rather than fabricate one.
• Approval-gate language guidance from AGENTS.md → Skill Authoring → "Positive prompts for approval gates" applies — script the question positively, list accepted replies.
• After the pass, if the section is empty, drop the heading entirely. If items remain, keep the heading with the surviving items.
• The "Pairs with issue-work" line at the top of SKILL.md stays; only the Stage 4.6 prompt + auto-invocation gets removed.

Acceptance criteria

• Stage 3 includes a default-on collaborative open-questions pass when the draft has one or more open questions
• The pass states the skill's lean per question (or "no lean") and accepts confirm / override / defer per question
• After the pass, the draft re-renders with resolved questions integrated into the right sections and the Open questions section trimmed accordingly
• User can opt out of the pass with post as-is or skip
• Stage 4.6 no longer prompts to invoke /issue-work; the completion report still shows URL + metadata + archive path
• CHANGELOG entry under [Unreleased]