feature-design-assistant
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
By davila7 · 567 installs
npx skills add davila7/claude-code-templates --skill feature-design-assistant
Source repository · Upstream listing
Feature Design Assistant
Help turn ideas into fully formed designs and specs through structured information gathering and collaborative validation.
Announce at start: "I'm using the feature design assistant skill to design this feature."
Phase 1: Context Discovery
First, explore the codebase to understand:
Project structure and tech stack
Existing patterns and conventions
Related features or modules
Recent changes in relevant areas
Phase 2: Structured Information Gathering
Use AskUserQuestion to batch collect information efficiently. Each call can ask up to 4 questions.
Round 1: Core Requirements (4 questions)
Round 2: Technical Requirements (4 questions)
Round 3: Integration & Dependencies (4 questions)
Round 4: Clarifying Questions (Context Dependent)
Based on previous answers, ask follow up questions. Examples:
If UI layer selected:
If High Security selected:
Phase 3: Approach Exploration
After gathering requirements, propose 2 3 approaches:
Use AskUserQuestion to confirm approach:
Phase 4: Design Presentation
Present design in sections (300 500 words each), validate after each:
1. Architecture Overview High level structure
2. Data Model Entities, relationships, schema
3. API Design Endpoints, request/response
4. Component Design Internal modules, interfaces
5. Error Handling Error cases, recovery strategies
6. Testing Strategy What and how to test
After each section, use AskUserQuestion:
Phase 5: Documentation & Tasks
Save Design Document
Write to docs/designs/YYYY MM DD <topic design.md :
Generate Implementation Tasks
Phase 6: Execution Handoff
Key Principles
Batch questions efficiently Use all 4 question slots when appropriate
Use multiSelect for non exclusive options Layers, features, requirements
Use single select for decisions Approach, timeline, strategy
Mark recommendations Add "(Recommended)" to preferred options
Progressive refinement General → Specific questions
Validate incrementally Check understanding at each phase
YAGNI ruthlessly Remove unnecessary features from designs