/silver:clarify

SB-orchestrated clarification workflow for vague ideas, sketched requirements, or full requirement docs that still need a decision-ready brief before gsd:discuss-phase can pick up.

Overview

/silver:clarify blends product framing, option generation, and convergence into a single workflow. It is the front end of planning: it takes ambiguity, sharpens the problem statement, and produces a handoff that gsd:discuss-phase can use without guessing.

It does not implement work or write plans. It helps the user compare options, pressure-test assumptions, and lock a recommendation. If the topic is visual or diagram-heavy, it can offer the browser-based visual companion before the deeper questions begin.

Good fits: vague ideas, rough feature briefs, requirement docs that still feel fuzzy, or decision points where the next implementation step is not obvious yet.

When to use

  • "I want to build..." / "I have an idea..." / "Here's my concept..."
  • "What's the best approach for..." / "Should we use X or Y?"
  • A requirement doc exists, but the decisions are still scattered or unclear
  • You want a decision-ready brief before entering GSD discuss-phase

Workflow steps

Step 0 — Load preferences

Read the silver-bullet.md §10 workflow preferences and apply stored routing or mode preferences silently.

Step 1 — Frame the problem

Restate the goal in plain language, identify who the user is, and note what "done" looks like. If the prompt is already detailed, compress the brief into a cleaner problem statement.

Step 2 — Explore options

Generate 2 to 4 plausible approaches, including a straightforward option and at least one more ambitious alternative. Keep the tradeoffs explicit.

Step 3 — Pressure-test

Check assumptions, highlight uncertainties, and flag anything that needs research or external validation before implementation starts.

Step 4 — Converge

Pick the best path for the current constraints and capture the rationale in a concise decision brief.

Step 5 — Handoff

Write .planning/CLARIFY.md and hand off to gsd:discuss-phase once the brief is clear enough for phase discussion.

Modes

  • Interactive - asks follow-up questions when the input is still fuzzy.
  • Autonomous - applies sensible defaults, logs decisions, and keeps moving until the brief is decision-ready.
  • Analyze - leans harder on context synthesis before asking questions.
  • Chain - continues directly into gsd:discuss-phase when the handoff is ready.

Output

The main artifact is .planning/CLARIFY.md. It should contain the problem framing, options considered, recommendation, and any follow-up questions that still need GSD discussion.

Example invocation

/silver:clarify I have a rough idea for a todo app feature, but I'm not sure what the exact scope should be.

The workflow frames the request, compares a few possible directions, converges on a recommendation, writes .planning/CLARIFY.md, and hands off to gsd:discuss-phase.