Skip to content

MuharremTozan/Agentic-Duel / .agent/skills/brainstorming

brainstorming

Verified

Use this skill before any creative or constructive work (features, components, architecture, behavior changes, or functionality). This skill transforms vague ideas into validated designs through disciplined, incremental reasoning and collaboration.

FileKindSize
SKILL.mdskill md5.0 KB
dynamic-questioning.mdmarkdown11.3 KB

dynamic-questioning.md

View on GitHub
# Dynamic Question Generation

> **PRINCIPLE:** Questions are not about gathering dataβ€”they are about **revealing architectural consequences**.
>
> Every question must connect to a concrete implementation decision that affects cost, complexity, or timeline.

---

## 🧠 Core Principles

### 1. Questions Reveal Consequences

A good question is not "What color do you want?" but:

```markdown
❌ BAD: "What authentication method?"
βœ… GOOD: "Should users sign up with email/password or social login?

   Impact:
   - Email/Pass β†’ Need password reset, hashing, 2FA infrastructure
   - Social β†’ OAuth providers, user profile mapping, less control

   Trade-off: Security vs. Development time vs. User friction"
```

### 2. Context Before Content

First understand **where** this request fits:

| Context | Question Focus |
|---------|----------------|
| **Greenfield** (new project) | Foundation decisions: stack, hosting, scale |
| **Feature Addition** | Integration points, existing patterns, breaking changes |
| **Refactor** | Why refactor? Performance? Maintainability? What's broken? |
| **Debug** | Symptoms β†’ Root cause β†’ Reproduction path |

### 3. Minimum Viable Questions

**PRINCIPLE:** Each question must eliminate a fork in the implementation road.

```
Before Question:
β”œβ”€β”€ Path A: Do X (5 min)
β”œβ”€β”€ Path B: Do Y (15 min)
└── Path C: Do Z (1 hour)

After Question:
└── Path Confirmed: Do X (5 min)
```

If a question doesn't reduce implementation paths β†’ **DELETE IT**.

### 4. Questions Generate Data, Not Assumptions

```markdown
❌ ASSUMPTION: "User probably wants Stripe for payments"
βœ… QUESTION: "Which payment provider fits your needs?

   Stripe β†’ Best documentation, 2.9% + $0.30, US-centric
   LemonSqueezy β†’ Merchant of Record, 5% + $0.50, global taxes
   Paddle β†’ Complex pricing, handles EU VAT, enterprise focus"
```

---

## πŸ“‹ Question Generation Algorithm

```
INPUT: User request + Context (greenfield/feature/refactor/debug)
β”‚
β”œβ”€β”€ STEP 1: Parse Request
β”‚   β”œβ”€β”€ Extract domain (ecommerce, auth, realtime, cms, etc.)
β”‚   β”œβ”€β”€ Extract features (explicit and implied)
β”‚   └── Extract scale indicators (users, data volume, frequency)
β”‚
β”œβ”€β”€ STEP 2: Identify Decision Points
β”‚   β”œβ”€β”€ What MUST be decided before coding? (blocking)
β”‚   β”œβ”€β”€ What COULD be decided later? (deferable)
β”‚   └── What has ARCHITECTURAL impact? (high-leverage)
β”‚
β”œβ”€β”€ STEP 3: Generate Questions (Priority Order)
β”‚   β”œβ”€β”€ P0: Blocking decisions (cannot proceed without answer)
β”‚   β”œβ”€β”€ P1: High-leverage (affects >30% of implementation)
β”‚   β”œβ”€β”€ P2: Medium-leverage (affects specific features)
β”‚   └── P3: Nice-to-have (edge cases, optimization)
β”‚
└── STEP 4: Format Each Question
    β”œβ”€β”€ What: Clear question
    β”œβ”€β”€ Why: Impact on implementation
    β”œβ”€β”€ Options: Trade-offs (not just A vs B)
    └── Default: What happens if user doesn't answer
```

---

## 🎯 Domain-Specific Question Banks

### E-Commerce

| Question | Why It Matters | Trade-offs |
|----------|----------------|------------|
| **Single or Multi-vendor?** | Multi-vendor β†’ Commission logic, vendor dashboards, split payments | +Revenue, -Complexity |
| **Inventory Tracking?** | Needs stock tables, reservation logic, low-stock alerts | +Accuracy, -Development time |
| **Digital or Physical Products?** | Digital β†’ Download links, no shipping | Physical β†’ Shipping APIs, tracking |
| **Subscription or One-time?** | Subscription β†’ Recurring billing, dunning, proration | +Revenue, -Complexity |

### Authentication

| Question | Why It Matters | Trade-offs |
|----------|----------------|------------|
| **Social Login Needed?** | OAuth providers vs. password reset infrastructure | +UX, -Control |
| **Role-Based Permissions?** | RBAC tables, policy enforcement, admin UI | +Security, -Development time |
| **2FA Required?** | TOTP/SMI infrastructure, backup codes, recovery flow | +Security, -UX friction |
| **Email Verification?** | Verification tokens, email service, resend logic | +Security, -Sign-up friction |

### Real-time

| Question | Why It Matters | Trade-offs |
|----------|----------------|------------|
| **WebSocket or Polling?** | WS β†’ Server scaling, connection management | Polling β†’ Simpler, higher latency |
| **Expected Concurrent Users?** | <100 β†’ Single server, >1000 β†’ Redis pub/sub, >10k β†’ specialized infra | +Scale, -Complexity |
| **Message Persistence?** | History tables, storage costs, pagination | +UX, -Storage |
| **Ephemeral or Durable?** | Ephemeral β†’ In-memory, Durable β†’ Database write before emit | +Reliability, -Latency |

### Content/CMS

| Question | Why It Matters | Trade-offs |
|----------|----------------|------------|
| **Rich Text or Markdown?** | Rich Text β†’ Sanitization, XSS risks | Markdown β†’ Simple, no WYSIWYG |
| **Draft/Publish Workflow?** | Status field, scheduled jobs, versioning | +Control, -Complexity |
| **Media Handling?** | Upload endpoints, storage, optimization | +Features, -Development time |
| **Multi-language?** | i18n tables, translation UI, fallback logic | +Reach, -Complexity |

---

## πŸ“ Dynamic Question Template

```markdown
Based on your request for [DOMAIN] [FEATURE]:

## πŸ”΄ CRITICAL (Blocking Decisions)

### 1. **[DECISION POINT]**

**Question:** [Clear, specific question]

**Why This Matters:**
- [Explain architectural consequence]
- [Affects: cost / complexity / timeline / scale]

**Options:**
| Option | Pros | Cons | Best For |
|--------|------|------|----------|
| A | [Advantage] | [Disadvantage] | [Use case] |
| B | [Advantage] | [Disadvantage] | [Use case] |

**If Not Specified:** [Default choice + rationale]

---

## 🟑 HIGH-LEVERAGE (Affects Implementation)

### 2. **[DECISION POINT]**
[Same format]

---

## 🟒 NICE-TO-HAVE (Edge Cases)

### 3. **[DECISION POINT]**
[Same format]
```

---

## πŸ”„ Iterative Questioning

### First Pass (3-5 Questions)
Focus on **blocking decisions**. Don't proceed without answers.

### Second Pass (After Initial Implementation)
As patterns emerge, ask:
- "This feature implies [X]. Should we handle [edge case] now or defer?"
- "We're using [Pattern A]. Should [Feature B] follow the same pattern?"

### Third Pass (Optimization)
When functionality works:
- "Performance bottleneck at [X]. Optimize now or acceptable for now?"
- "Refactor [Y] for maintainability or ship as-is?"

---

## 🎭 Example: Full Question Generation

```
USER REQUEST: "Build an Instagram clone"

STEP 1: Parse
β”œβ”€β”€ Domain: Social Media
β”œβ”€β”€ Features: Photo sharing, engagement (likes/comments), user profiles
β”œβ”€β”€ Implied: Feed, following, authentication
└── Scale: Potentially high (social apps go viral)

STEP 2: Decision Points
β”œβ”€β”€ Blocking: Storage strategy, authentication method, feed type
β”œβ”€β”€ High-leverage: Real-time notifications, data model complexity
└── Deferable: Analytics, advanced search, reels/video

STEP 3: Generate Questions (Priority)

P0 (Blocking):
1. Storage Strategy β†’ Affects architecture, cost, speed
2. Feed Algorithm β†’ Affects database queries, complexity
3. Auth Method β†’ Affects dev time, UX, security

P1 (High-leverage):
4. Real-time Notifications β†’ WebSocket vs polling
5. Media Processing β†’ Client-side vs server-side optimization

P2 (Deferable):
6. Story/Reels β†’ Major feature creep, defer to v2
7. DM/Chat β†’ Separate subsystem, defer to v2

STEP 4: Format Output
```

---

## πŸ“Š Generated Output (Example)

```
Based on your Instagram clone request:

## πŸ”΄ CRITICAL DECISIONS (Cannot Proceed Without Answers)

### 1. **Photo Storage Strategy**

**Question:** Where will user photos be stored and served?

**Why This Matters:**
- Affects: Monthly hosting costs, page load speed, CDN complexity
- High-volume social apps: 1000 users Γ— 10 photos Γ— 2MB = 20GB storage

**Options:**
| Option | Cost | Speed | Complexity | Best For |
|--------|------|-------|------------|----------|
| **Cloudinary** | $89/mo (25GB) | Fast (CDN) | Low | MVP, rapid launch |
| **AWS S3 + CloudFront** | $0.023/GB | Fast (CDN) | Medium | Production, cost-optimized |
| **Supabase Storage** | Free tier 1GB | Medium | Low | Small scale, simple |
| **Local Storage** | Server cost | Slow | Low | Development only |

**If Not Specified:** Cloudinary (balanced for MVP)

---

### 2. **Feed Algorithm Choice**

**Question:** How should the main feed work?

**Why This Matters:**
- Affects: Database query complexity, caching strategy, development time
- Algorithmic feeds require ML infrastructure, ranking signals

**Options:**
| Option | Complexity | Database Impact | Best For |
|--------|------------|-----------------|----------|
| **Chronological** | Low | Simple query | Early stage, transparency |
| **Follow-Only** | Medium | JOIN with pagination | Most social apps |
| **Algorithmic** | High | Pre-computed feed tables | Instagram competitor |

**If Not Specified:** Follow-Only (balanced for social app)

---

### 3. **Authentication Approach**

**Question:** How do users sign up and login?

**Why This Matters:**
- Affects: Development time (2-5 hours), security posture, UX friction

**Options:**
| Option | Dev Time | Security | UX | Best For |
|--------|----------|----------|-----|----------|
| **Email/Password** | 4-5 hrs | High (if 2FA) | Medium | Full control needed |
| **Social Only** | 1-2 hrs | Provider-dependent | Smooth | B2C, rapid launch |
| **Magic Link** | 2-3 hrs | Medium | Very smooth | Security-focused |
| **Clerk/Auth0** | 1 hr | High | Smooth | Fastest to market |

**If Not Specified:** Clerk (fastest for MVP)

---

## 🟑 HIGH-LEVERAGE (Affects Architecture)

### 4. **Real-time Notifications**

**Question:** Do users need instant notifications for likes/comments?

**Why This Matters:**
- WebSocket adds infrastructure complexity (Redis pub/sub for scaling)
- Polling is simpler but higher latency

**Options:**
| Option | Complexity | Scale Cost | Best For |
|--------|------------|------------|----------|
| **WebSocket + Redis** | High | $10+/mo | >1000 concurrent users |
| **Polling (30s)** | Low | DB queries | <1000 users |
| **No Real-time** | None | None | MVP, validate first |

**If Not Specified:** Polling for MVP (defer WebSocket until validated)

---

## 🟒 NICE-TO-HAVE (Defer to v2)

### 5. **Video/Reels Support**
- Major complexity (video processing, streaming infrastructure)
- Recommendation: Launch with photos only, add video after validation

### 6. **Direct Messaging**
- Separate subsystem (chat infrastructure different from feed)
- Recommendation: Use Pusher/Stream for real-time or defer entirely

---

## πŸ“‹ Summary

| Decision | Recommendation | If Changed |
|----------|----------------|------------|
| Storage | Cloudinary | +3 hrs setup |
| Feed | Follow-only | +2 hrs query optimization |
| Auth | Clerk | -3 hrs dev time |
| Real-time | Polling | +5 hrs WebSocket setup |
| Video | Defer to v2 | N/A |
| DM | Defer to v2 | N/A |

**Total Estimated MVP Time:** 15-20 hours with recommendations above
```

---

## 🎯 Principles Recap

1. **Every question = Architectural decision** β†’ Not data gathering
2. **Show trade-offs** β†’ User understands consequences
3. **Prioritize blocking decisions** β†’ Cannot proceed without
4. **Provide defaults** β†’ If user doesn't answer, we proceed anyway
5. **Domain-aware** β†’ Ecommerce questions β‰  Auth questions β‰  Real-time questions
6. **Iterative** β†’ More questions as patterns emerge during implementation
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall