SkillsAdd

smithery.ai

design-doc-interviewer

Interview the user to turn a proposed product/engineering change into a structured design document.

First seen Mar 20, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Summary

  • Interview the user to turn a proposed product/engineering change into a structured design document.
  • Use when the user asks to be interviewed, wants help clarifying a design, or wants a design doc produced from Q&A.
  • Emphasize numbered questions (few at a time), capture requirements/constraints/UX/data/logic/testing, and output a clean design doc.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Shared topics
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Shared topics
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
azure-rbac Shared topics
microsoft/azure-skills 489K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
building-native-ui Shared topics
expo/skills 59.2K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,636 B
  • docs SUMMARY.md 377 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Design Doc Interviewer

Overview

Elicit the minimum set of decisions and details needed to produce a clear design document, using short, numbered question batches and progressive refinement.

Workflow

1) Align on format and scope

  • Ask for the intended audience, affected systems, and whether there is a preferred template or example to mirror.
  • If the user provided a sample doc, follow its section order and tone.
  • Identify the target package in this monorepo. If unclear, ask the user to pick one of the packages managed here before proceeding.

1.5) Pre-flight repo context

  • Search design/* with emphasis on design/ideas/ for related context before asking detailed questions.
  • Summarize any relevant findings and confirm whether they should be incorporated.

2) Run a structured interview in small batches

  • Ask 2–4 numbered questions per turn.
  • Keep questions concise, unambiguous, and grouped by section.
  • After each response, confirm key points and update the working outline.

Use the question bank when needed: references/question-bank.md.

3) Draft the design doc incrementally

  • Populate sections as soon as sufficient information is available.
  • Mark unknowns as Open Questions rather than blocking progress.
  • Use the template for consistent structure: references/design-doc-template.md.

4) Review for completeness and risk

  • Check for missing: goals/non-goals, data model/API changes, compatibility, rollout, testing.
  • Ask final clarifying questions only for high-impact gaps.

5) Deliver the final document

  • Output a clean, single-pass doc with headings and code fences where needed.
  • Preserve the user’s terminology and system names.
  • Always save the final design doc at design/{package}/ where {package} is a package managed in this monorepo. Create the directory if it does not exist.

Interview Style Rules

  • Number all questions.
  • Keep question batches small (2–4).
  • Prefer concrete, scenario-based prompts over abstract ones.
  • Avoid asking about sections the user explicitly scoped out.

References

  • references/design-doc-template.md for the canonical structure.
  • references/question-bank.md for section-specific prompts.