docs: support alternative edit strategies

SKILL.md

@@ -68,6 +68,8 @@ Ask the user for:
 
 Before transcribing, ask the user what they want to do with the video. User requirements are often vague in the first pass — that's expected. The plan is refined iteratively.
 
+For full video-edit planning requests, ask early whether the user wants **one focused recommended cut** or **multiple alternative editing strategies**. If they want alternatives, analyze a wider set of candidate segments and present modular options the user can freely combine into their own final cut. Do not force the plan into a rigid one-path timeline where every section has only one fixed choice.
+
 If the agent's runtime supports structured questioning (e.g., a `clarify` tool or a `grill-me` skill), use it to gather requirements systematically. Ask questions one at a time with multiple-choice options — this is much more effective than a free-text wall of questions.
 
 **The requirements questionnaire below covers the key axes for gameplay/creator video editing.** Not every question applies to every session — pick the relevant ones based on the user's initial request. See `references/editing-requirements-questionnaire.md` for the full questionnaire with choices.
@@ -76,6 +78,7 @@ If the agent's runtime supports structured questioning (e.g., a `clarify` tool o
 |---|---|
 | Target platform (B站/抖音/YouTube/Shorts) | Determines aspect ratio, pacing, subtitle density, meme/热梗 density |
 | Narrative style (搞笑集锦/故事线+搞笑/高光混剪) | Determines structure: pure clip reel vs. narrative arc with 起承转合 |
+| Planning mode (single recommended cut / multiple alternatives) | Determines whether to produce one focused timeline or modular strategy options the user can mix and match |
 | Role distribution (主视角/平权联机/主持人) | Determines whose voice/reactions to prioritize in cuts |
 | Effect density (少量/中等/高密度) | Determines how many 表情包/贴纸/特效 to search for and apply |
 | Editor tool (Premiere Pro/剪映/DaVinci/必剪) | Determines how specific transition/effect instructions are phrased |
@@ -322,7 +325,7 @@ For fast-paced story + comedy gameplay videos, cull hard: keep combat, danger, r
 
 This workflow is especially effective for requests like **“find fast-paced funny + story-driven candidate segments”**. It keeps token/runtime cost low while still verifying whether a transcript-highlighted moment actually has usable on-screen action.
 
-Output a Markdown table with overall recommendations, then let the user iterate. **Respond in the same language the user is using.** If the plan is likely to be long (large tables, detailed scripts, full requirement summaries, or multi-section recommendations), ask whether the user wants it saved as a file instead of pasted into chat. Default to Markdown (`.md`) for saved plans unless the user requests another format.
+Output a Markdown table with overall recommendations, then let the user iterate. **Respond in the same language the user is using.** If the user requested multiple alternative strategies, structure the plan as modular options rather than a single rigid timeline: offer alternative openings, narrative arcs, pacing choices, candidate segments, transitions, BGM/effect directions, and optional inserts the user can mix and match. In this mode, analyze more candidate segments than strictly needed for one final cut, and clearly label tradeoffs (e.g., funniest, clearest story, fastest pacing, most emotional, best visual action). If the plan is likely to be long (large tables, detailed scripts, full requirement summaries, or multi-section recommendations), ask whether the user wants it saved as a file instead of pasted into chat. Default to Markdown (`.md`) for saved plans unless the user requests another format.
 
 ```markdown
 ## Edit Plan
@@ -339,6 +342,14 @@ Output a Markdown table with overall recommendations, then let the user iterate.
 | 00:01:45–00:02:10 | 25s      | Walking, no dialogue or event   | Cut           | —          | —                  |
 | 00:02:10–00:02:35 | 25s      | Combat starts, highlight moment | Keep, slow-mo | Fade in    | Sync to BGM rhythm |
 | ...               | ...      | ...                             | ...           | ...        | ...                |
+
+### Alternative Strategy Options (if requested)
+
+| Module | Option | Best for | Candidate segments | Tradeoffs |
+| ------ | ------ | -------- | ------------------ | --------- |
+| Opening | Cold open with funniest quote | Fast hook | 00:03:10–00:03:24 / 00:18:40–00:19:05 | Strong hook, weaker story setup |
+| Story arc | Slow setup → escalation → payoff | Clear narrative | 00:01:20–00:02:30 / 00:12:00–00:14:10 / 00:22:30–00:23:20 | Better story, slower pacing |
+| Insert | Short visual gag bridge | Rhythm reset | 00:08:10–00:08:16 | Optional; use only if pacing feels too dense |
 ```
 
 **Completion criteria:** user receives a Markdown table addressing their stated goal, and is invited to ask follow-up questions.
@@ -442,6 +453,7 @@ This creates an isolated venv with `funasr`, `torch`, `torchaudio`. If the user
 13. **Choosing command syntax or execution environment solely from where the agent runs.** Choose based on where the video file lives and where the command will execute. Windows execution → PowerShell commands and Windows paths; WSL/Linux execution → Linux shell commands and Linux paths. If the agent runs in WSL but Windows execution is chosen, use `powershell.exe` to do lightweight setup (copy files, install/check dependencies, run `uv sync`) before handing only the long transcription command to the user. Never ask Windows `uv` to run from `\\\\wsl.localhost\\...` / `\\\\wsl$\\...`.
 14. **Saying you'll provide a command but not including it.** If you mention giving the user a transcription command, include it immediately in that same response. Do not move on to other content without printing the actual command. The user should never have to ask for it.
 15. **Sending a wall of free-text questions.** When gathering editing requirements, use structured one-at-a-time multiple-choice questions via the runtime's clarify/prompt tool. This is far more effective than dumping 10 questions as a paragraph.
+16. **Making full edit plans too rigid.** For complete planning requests, ask whether the user wants multiple alternative strategies. If yes, provide modular options and extra candidate segments that the user can combine, rather than a single fixed linear plan where every section has exactly one prescribed choice.
 
 ## Verification checklist