sketchlisted

# Sketch — Divergent Generation Fan out N parallel variants of the same thing. Browse results, cherry-pick, combine. `$ARGUMENTS` = what to generate variants of. Can be anything: a dashboard, an API design, a data pipeline, a component, an algorithm. If `$ARGUMENTS` is empty, ask what to generate before proceeding. <orchestrator_workflow> <step name="clarify"> Before spawning anything: - Is the task clear enough to fan out? If vague or too broad, ask first. Don't spawn 5 agents toward a fuzzy target. - What kind of task is this? GUI/visual vs code/architecture vs mixed - What dimensions should vary? (layout, style, data structure, algorithm, API shape...) - What stays constant? (same data, same endpoints, same requirements) - How many variants? Default 5. User can override with `N=3` in arguments. </step> <step name="design"> Each variant needs a clear angle — not just "variant 1, variant 2." Name them by what makes them different: <example> Dashboard task → "dense-grid", "single-focus", "sidebar-nav", "card-mosaic", "terminal-aesthetic" Auth system → "jwt-stateless", "session-based", "oauth-delegated", "passkey-first", "hybrid-jwt-session" Data pipeline → "streaming", "batch-with-checkpoints", "event-sourced", "cqrs-split", "simple-cron" </example> State your variant strategy before spawning. Keep it brief. </step> <step name="spawn"> Spawn `general-purpose` agents — all in ONE message for true parallelism. Determine which instruction block applies (GUI or non-GUI