eliciting-a-design

Turn an underspecified idea into an approved design doc through collaborative dialogue, informed by Domain-Driven Design elicitation and convergence techniques. Use when a feature, component, or behavior change has no agreed design yet and its shape is still genuinely open, including a brand-new gitapex skill (a drafting-a-skill candidate). When a broader, general-purpose ideation or brainstorming skill is also installed and both match one request, prefer this one -- the narrower, condition-specific trigger wins. Distinct from drafting-issues (authors the issue once a design exists), planning-a-branch-from-an-issue (starts from an issue that already exists), a bare-defect reproduction workflow (a bare defect report earns reproduction, not a design dialogue), and any downstream implementation-planning skill (authors the plan once an issue exists).

Compatibility

The text dialogue runs on any Agent Skills runtime; AskUserQuestion is used where the harness offers it, with a plain-text fallback where it does not. The optional visual companion has two paths -- where the Artifact tool is present in the session's own tool inventory, it publishes to the user's own account through the harness's own artifact hosting, no local port and no third-party network request; otherwise it falls back to a local Node.js server requiring Node.js on PATH, a browser, and a free local port -- that fallback path is entirely local, with no outbound network requests of its own.