wipnotespec-from-slicelisted

# Spec from Slice — interview + generate Use this skill to capture Scope, Decisions, and Context for one slice of an active plan, then materialise the resulting feature's OpenSpec-formatted spec into its HTML — in a single guided pass. This skill is a Claude-only convenience layer. The canonical interface is the cross-harness CLI command `wipnote plan elicit-decisions`, which works on Codex CLI and Gemini CLI without any of the steps below. ## When to invoke - Plan slice has just been approved and you are about to call `wipnote plan promote-slice`. - Slice has been promoted and the resulting feature has no `<section class="spec">` yet, or the section is empty. - Decisions changed and you want to re-elicit and re-generate the spec. ## Inputs you need - `<plan-id>` — the active plan that owns the slice. - `<slice-num>` — the integer slice number within that plan. If the slice already has `feature_id` set, the skill will reuse it for the generate step. Otherwise it stops after writing the decisions and points the user at `wipnote plan promote-slice` first. ## Procedure 1. **Read the slice card.** Run `wipnote plan show <plan-id>` (or read `.wipnote/plans/<plan-id>.yaml` directly) to find the slice with the given `num`. Capture `title`, `what`, `why`, `done_when`, `tests`, and current `decisions_notes` (if any). 2. **Re-elicitation guard.** If `decisions_notes` is non-empty, ask the user via `AskUserQuestion`: - **Re-elicit** — overwrite previous note