feature-design-assistant

Topics in the source

• Feature Design Assistant
• Phase 1: Context Discovery
• Phase 2: Structured Information Gathering
• Round 1: Core Requirements (4 questions)
• Round 2: Technical Requirements (4 questions)
• Round 3: Integration & Dependencies (4 questions)
• Round 4: Clarifying Questions (Context-Dependent)
• Phase 3: Approach Exploration

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." First, explore the codebase to understand: Project structure and tech stack Existing patterns and conventions Related features or modules Recent changes in relevant areas Use AskUserQuestion to batch collect information efficiently. Each call can ask up to 4 questions. Based on previous answers, ask follow-up questions. Examples: If UI layer selected: If High Security selected: After gathering requirements, propose 2-3 approaches: Use AskUserQuestion to confirm approach: 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: Write to docs/designs/YYYY-MM-DD- -design.md: Batch questions efficiently - Use all 4 question slots when appropr

This is an excerpt. Refer to the complete source and its current requirements.