proposal-builder

# Proposal Builder

Transform vague feature requests into structured proposals through interactive Q&A.

## Purpose

When users provide simple requests like "implement notifications on Laravel 12.x" or "add user authentication", this skill guides them through clarifying questions to generate a complete, structured proposal ready for judgement.

## Input

Raw user request (string) - can be as vague as:
- "add notifications"
- "implement auth on Laravel"
- "make the app faster"

## Process

### Step 1: Analyze Request Completeness

Check if the request contains:
- Feature description (what)
- Goals/objectives (why)
- Requirements (specific needs)
- Constraints (limitations)
- Success criteria (how to measure)

If missing 2+ critical sections → Launch interactive builder

### Step 2: Detect Feature Type & Framework

Extract from request:
- **Feature type**: auth, notifications, payment, search, API, UI, performance, etc.
- **Framework/tech stack**: Laravel, React, Vue, Django, Express, etc.
- **Keywords**: for codebase search later

### Step 3: Ask Contextual Clarifying Questions

Use AskUserQuestion tool to gather missing information.

**Question Strategy:**
- One question at a time
- Multiple choice options (easier than open-ended)
- 3-5 questions typically sufficient
- Questions adapt based on feature type and framework

**Common Question Templates:**

**For ANY feature:**
```
Q: What's the main goal of this feature?
Options:
- Solve specific user pain point (describe in "Other")
- Business requirement
- Technical improvement
- Competitive parity

Q: What are the key requirements?
Options:
- Just basic functionality
- Production-ready with error handling
- Enterprise-grade with monitoring
- MVP to validate concept

Q: Any technical constraints?
Options:
- Must use existing [detected framework] patterns
- Cannot break backward compatibility
- Must integrate with [detected systems]
- No constraints

Q: How will you measure success?
Options:
- Just working is enough
-