jnuyens/bm:sketch

<objective> Explore design directions through throwaway HTML mockups before committing to implementation. Each sketch produces 2-3 variants for comparison. Sketches live in `.planning/sketches/` and integrate with GSD commit patterns, state tracking, and handoff workflows. Loads spike findings to ground mockups in real data shapes and validated interaction patterns.

Two modes:

• Idea mode (default) — describe a design idea to sketch
• Frontier mode (no argument or "frontier") — analyzes existing sketch landscape and proposes consistency and frontier sketches

Does not require /bm:new-project — auto-creates .planning/sketches/ if needed. </objective>

<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/sketch.md @${CLAUDE_PLUGIN_ROOT}/references/ui-brand.md @${CLAUDE_PLUGIN_ROOT}/references/sketch-theme-system.md @${CLAUDE_PLUGIN_ROOT}/references/sketch-interactivity.md @${CLAUDE_PLUGIN_ROOT}/references/sketch-tooling.md @${CLAUDE_PLUGIN_ROOT}/references/sketch-variant-patterns.md </execution_context>

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. </runtime_note>

<context> Design idea: $ARGUMENTS

Available flags:

• --quick — Skip mood/direction intake, jump straight to decomposition and building. Use when the design direction is already clear. </context>

<process> Execute the sketch workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/sketch.md end-to-end. Preserve all workflow gates (intake, decomposition, target stack research, variant evaluation, MANIFEST updates, commit patterns). </process>