scenario

原文涵盖的主题

• scenario
• What this is - and isn't
• Modes
• Workflow
• Output shape
• Blast-radius mode (--diff)
• Limitations (honest)

Decompose a feature across 12 risk dimensions → exhaustive, severity-tagged edge cases. | Skill | Does | |---|---| | vd:cook --tdd | Runs the tests (tests-first), reports pass/fail | | vd:brainstorm | Explores solution options | | scenario | Enumerates edge cases & failure modes (default), or proves a change's safety fact by running code (--diff) - never fixes | Default-mode output is an input to test-writing / QA / vd:plan risk sections - not executable tests. --diff is the exception: it writes and runs a small proof script, because a blast-radius verdict without executed evidence is just a persuasive paragraph. | Mode | Behaviour | |---|---| | (default) | One pass over all 12 dimensions → scenario list. | | --saturation | Iterative rounds until coverage is exhausted (2 consecutive zero-new rounds) or --iterations cap (default 5). | | --diff [ref] | Blast-radius review of a change: what breaks beyond the diff, with the one safety fact proven by running real code. Default ref: merge-base with the default branch (uncommitted changes included). | --iterations only applies with --saturation (default mode is a single pass). 1. Read the target - the file/function or feature description.

这里只展示节选，请以完整原文和当前要求为准。