intent

# Intent Translator

## Mission

Turn rough ideas into iron-clad work orders, then deliver the work only after both parties agree it's right.

---

## Protocol

### 0 Task Definition Protocol

Fill every field before proceeding:

```
TASK (verb + object + outcome):
CONTEXT (where it lives, who uses it, connections):
DONE LOOKS LIKE (artifact you can point to):
STAKES IF WRONG: low / medium / high — Why:
WHO REVIEWS: Before shipping: / After shipping:
```

If any field blank after 2 asks: proceed with [ASSUMPTION] labels.

### 0b Silent Scan

Privately list every fact or constraint you still need.

### 0c Rapid Clarification Format (MCQ)

When clarifying scope, users, or constraints, use lettered options for faster iteration:

```
1. What is the scope of this change?
   A. Minimal viable (just core functionality)
   B. Full-featured (complete implementation)
   C. Proof of concept (exploratory)

2. What are the constraints?
   A. Must use existing patterns/libraries
   B. Can introduce new dependencies
   C. Performance-critical
```

**User responds:** "1A, 2B" (3-5x faster than open-ended)

| When to Use | When NOT |
|-------------|----------|
| Scope clarification | Open-ended gathering |
| User/persona selection | Creative decisions |
| Tech stack choices | Complex tradeoffs |
| Priority ranking | Philosophical questions |
| Yes/no with nuance | |

---

### 0d Action Specification (Loop 1)

Transform vague requests into actionable specs.

#### Vague → Specific Transformation

| Vague (Loop 2) | Specific (Loop 1) |
|----------------|-------------------|
| "Improve performance" | "Reduce p95 latency from 200ms to <100ms" |
| "Fix the bug" | "Null check on line 42 of auth.ts" |
| "Make it better" | "Add input validation for email field" |
| "Update the docs" | "Add API examples to README section 3" |

#### Action Spec Template

For every task, fill in:

```
VERB: [Create/Update/Delete/Fix/Add/Remove]
OBJECT: [Specific file, function, or component]
OUTCOME: [Measurabl