Feature Design Assistant

作者 davila78da17d671b6f無授權條款32K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

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.

僅含說明Software DevelopmentProductivity & Workflow
AI 產生的概覽

透過結構化提問引導協作式功能設計，產出設計文件與實作任務清單。

功能
此技能以六個階段的對話推進：先探查程式碼庫，再批次提出關於需求、範圍、品質屬性與整合的問題，並提出二到三種實作方案。接著分節呈現設計並逐節確認，涵蓋架構、資料模型、API、元件、錯誤處理與測試策略。它會把設計文件寫入 docs/designs/YYYY-MM-DD- -design.md，並產生附優先順序的實作任務清單，最後交接給執行階段。
適用情境
適用於規劃新功能、設計架構或對程式碼庫進行較大變更，並希望在動手寫程式前蒐集並確認需求的情境。也適合偏好先審閱設計、再進入實作的團隊。
執行需求
僅為指令，不含腳本。需要智慧代理能檢視程式碼庫並批次提出多選問題，且會在儲存庫中寫入 Markdown 設計文件。

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)

json
{  "questions": [    {      "question": "What is the primary goal of this feature?",      "header": "Goal",      "multiSelect": false,      "options": [        { "label": "New Functionality", "description": "Add entirely new capability to the system" },        { "label": "Enhancement", "description": "Improve or extend existing feature" },        { "label": "Bug Fix", "description": "Fix incorrect behavior or issue" },        { "label": "Refactoring", "description": "Improve code quality without changing behavior" }      ]    },    {      "question": "Who are the primary users of this feature?",      "header": "Users",      "multiSelect": true,      "options": [        { "label": "End Users", "description": "External customers using the product" },        { "label": "Admins", "description": "Internal administrators or operators" },        { "label": "Developers", "description": "Other developers using APIs or SDKs" },        { "label": "System", "description": "Automated processes or background jobs" }      ]    },    {      "question": "What is the expected scope of this feature?",      "header": "Scope",      "multiSelect": false,      "options": [        { "label": "Small (1-2 days)", "description": "Single component, limited changes" },        { "label": "Medium (3-5 days)", "description": "Multiple components, moderate complexity" },        { "label": "Large (1-2 weeks)", "description": "Cross-cutting concerns, significant changes" },        { "label": "Unsure", "description": "Need to explore further to estimate" }      ]    },    {      "question": "Are there any hard deadlines or constraints?",      "header": "Timeline",      "multiSelect": false,      "options": [        { "label": "Urgent", "description": "Need this ASAP, within days" },        { "label": "This Sprint", "description": "Should be done within current sprint" },        { "label": "Flexible", "description": "No hard deadline, quality over speed" },        { "label": "Planning Only", "description": "Just designing now, implementing later" }      ]    }  ]}

Round 2: Technical Requirements (4 questions)

json
{  "questions": [    {      "question": "Which layers of the system will this feature touch?",      "header": "Layers",      "multiSelect": true,      "options": [        { "label": "Data Model", "description": "Database schema, models, migrations" },        { "label": "Business Logic", "description": "Services, domain logic, rules" },        { "label": "API", "description": "REST/GraphQL endpoints, contracts" },        { "label": "UI", "description": "Frontend components, user interface" }      ]    },    {      "question": "What are the key quality requirements?",      "header": "Quality",      "multiSelect": true,      "options": [        { "label": "High Performance", "description": "Must handle high load or be very fast" },        { "label": "Strong Security", "description": "Sensitive data, auth, access control" },        { "label": "High Reliability", "description": "Cannot fail, needs redundancy" },        { "label": "Easy Maintenance", "description": "Needs to be easily understood and modified" }      ]    },    {      "question": "How should errors be handled?",      "header": "Errors",      "multiSelect": false,      "options": [        { "label": "Fail Fast", "description": "Stop immediately on any error" },        { "label": "Graceful Degrade", "description": "Continue with reduced functionality" },        { "label": "Retry & Recover", "description": "Automatic retry with recovery logic" },        { "label": "Context Dependent", "description": "Different strategies for different cases" }      ]    },    {      "question": "What testing approach is preferred?",      "header": "Testing",      "multiSelect": false,      "options": [        { "label": "TDD (Recommended)", "description": "Write tests first, then implementation" },        { "label": "Test After", "description": "Implement first, add tests after" },        { "label": "Minimal Tests", "description": "Only critical path testing" },        { "label": "No Tests", "description": "Skip testing for this feature" }      ]    }  ]}

Round 3: Integration & Dependencies (4 questions)

json
{  "questions": [    {      "question": "Does this feature need external integrations?",      "header": "Integrations",      "multiSelect": true,      "options": [        { "label": "Database", "description": "New tables, queries, or migrations" },        { "label": "External APIs", "description": "Third-party service calls" },        { "label": "Message Queue", "description": "Async processing, events" },        { "label": "None", "description": "No external integrations needed" }      ]    },    {      "question": "Are there dependencies on other features or teams?",      "header": "Dependencies",      "multiSelect": true,      "options": [        { "label": "Auth System", "description": "User authentication or authorization" },        { "label": "Other Features", "description": "Depends on features being developed" },        { "label": "External Team", "description": "Needs input from another team" },        { "label": "None", "description": "Fully independent feature" }      ]    },    {      "question": "How should we handle backwards compatibility?",      "header": "Compat",      "multiSelect": false,      "options": [        { "label": "Must Maintain", "description": "Cannot break existing clients" },        { "label": "Version API", "description": "Create new version, deprecate old" },        { "label": "Breaking OK", "description": "Can make breaking changes" },        { "label": "Not Applicable", "description": "New feature, no existing users" }      ]    },    {      "question": "What documentation is needed?",      "header": "Docs",      "multiSelect": true,      "options": [        { "label": "API Docs", "description": "Endpoint documentation" },        { "label": "User Guide", "description": "How-to for end users" },        { "label": "Dev Guide", "description": "Technical implementation details" },        { "label": "None", "description": "No documentation needed" }      ]    }  ]}

Round 4: Clarifying Questions (Context-Dependent)

Based on previous answers, ask follow-up questions. Examples:

If UI layer selected:

json
{  "questions": [    {      "question": "What UI framework/approach should we use?",      "header": "UI Tech",      "multiSelect": false,      "options": [        { "label": "React", "description": "React components with hooks" },        { "label": "Vue", "description": "Vue.js components" },        { "label": "Server-Side", "description": "Server-rendered HTML templates" },        { "label": "Existing Pattern", "description": "Follow current project conventions" }      ]    }  ]}

If High Security selected:

json
{  "questions": [    {      "question": "What security measures are required?",      "header": "Security",      "multiSelect": true,      "options": [        { "label": "Input Validation", "description": "Strict input sanitization" },        { "label": "Rate Limiting", "description": "Prevent abuse and DoS" },        { "label": "Audit Logging", "description": "Track all sensitive actions" },        { "label": "Encryption", "description": "Encrypt data at rest/transit" }      ]    }  ]}

Phase 3: Approach Exploration

After gathering requirements, propose 2-3 approaches:

markdown
## Approach Options
### Option A: [Name] (Recommended)**Pros:** ...**Cons:** ...**Best for:** ...
### Option B: [Name]**Pros:** ...**Cons:** ...**Best for:** ...
### Option C: [Name]**Pros:** ...**Cons:** ...**Best for:** ...

Use AskUserQuestion to confirm approach:

json
{  "questions": [    {      "question": "Which approach would you like to proceed with?",      "header": "Approach",      "multiSelect": false,      "options": [        { "label": "Option A (Recommended)", "description": "Brief summary of approach A" },        { "label": "Option B", "description": "Brief summary of approach B" },        { "label": "Option C", "description": "Brief summary of approach C" }      ]    }  ]}

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:

json
{  "questions": [    {      "question": "Does this section look correct?",      "header": "Review",      "multiSelect": false,      "options": [        { "label": "Looks Good", "description": "Continue to next section" },        { "label": "Minor Changes", "description": "Small adjustments needed" },        { "label": "Major Revision", "description": "Significant changes required" },        { "label": "Questions", "description": "Need clarification before proceeding" }      ]    }  ]}

Phase 5: Documentation & Tasks

Save Design Document

Write to docs/designs/YYYY-MM-DD-<topic>-design.md:

markdown
# Feature: [Name]
## Summary[Brief description]
## Requirements[From Phase 2 answers]
## Architecture[From Phase 4]
## Implementation Tasks[Task checklist]

Generate Implementation Tasks

markdown
## Implementation Tasks
- [ ] **Task Title** `priority:1` `phase:model` `time:15min`  - files: src/file1.py, tests/test_file1.py  - [ ] Write failing test for X  - [ ] Run test, verify it fails  - [ ] Implement minimal code  - [ ] Run test, verify it passes  - [ ] Commit
- [ ] **Another Task** `priority:2` `phase:api` `deps:Task Title` `time:10min`  - files: src/api.py  - [ ] Write failing test  - [ ] Implement and verify  - [ ] Commit

Phase 6: Execution Handoff

json
{  "questions": [    {      "question": "How would you like to proceed with implementation?",      "header": "Next Step",      "multiSelect": false,      "options": [        { "label": "Execute Now", "description": "Run /feature-pipeline in this session" },        { "label": "New Session", "description": "Start fresh session for implementation" },        { "label": "Later", "description": "Save design, implement manually later" },        { "label": "Revise Design", "description": "Go back and modify the design" }      ]    }  ]}

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

來源與署名

來源：davila7/claude-code-templates位於cli-tool/components/skills/development/feature-design-assistant提交8da17d6

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 davila7/claude-code-templates 的技能

React Best Practices

davila7

針對 React 與 Next.js 的效能指南，包含 40 多條關於瀑布請求、打包體積、渲染與重渲染的規則。

包含腳本
Software Development32K今天更新

Web Performance Optimization

davila7

指導開發者量測並修正網頁效能問題，例如核心網頁指標、打包體積、圖片與快取。

Software Development32K今天更新

Find Bugs

davila7

審查本機分支變更中的缺陷、安全漏洞與程式碼品質問題，只回報發現而不修改程式碼。

Security32K今天更新

Browser Automation

davila7

指導使用 Playwright 與 Puppeteer 進行瀏覽器自動化，用於測試、擷取與代理瀏覽器控制。

Software Development32K今天更新

Code Review

davila7

依循 Sentry 工程實務指導程式碼審查，涵蓋安全性、效能、測試與設計。

Software Development32K今天更新

Commit

davila7

依照 Sentry 的約定式提交規範格式化 Git 提交訊息，包含問題引用。

Software Development32K今天更新

更多Software Development技能

Playground

anthropics

精選

建立自成一體的互動式 HTML 遊樂場，包含控制項、即時預覽與可複製的提示詞輸出。

Software Development37K今天更新

M5 Onboard

anthropics

精選

透過 USB 偵測 M5Stack ESP32 開發板，燒錄 UIFlow 2.0 韌體並安裝 MicroPython 應用程式套件。

Software Development37K今天更新

Cardputer Buddy

anthropics

精選

指導迭代 Cardputer-Adv 的 MicroPython 應用程式套件：新增應用程式、透過 USB 序列埠推送檔案、查看日誌並執行 REPL 指令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精選

依據從遠端來源取得的 Web Interface Guidelines 審查 UI 程式碼，並以 file:line 形式回報問題。

Software Development32K5 週前更新

Vercel React Native Skills

vercel-labs

精選

React Native 與 Expo 最佳實務規則，涵蓋清單效能、動畫、導覽、UI 模式、狀態與 monorepo 設定。

Software Development32K5 週前更新

Vercel React Best Practices

vercel-labs

精選

Vercel 的 React 與 Next.js 效能指南，以 70 條規則的形式用於撰寫、審查與重構程式碼。

Software Development32K5 週前更新