# /feature - View Feature Priority Queue

When the user runs `/feature`, read and display the feature queue from SYSTEM-INTEL.md.

## Steps

1. **Read the priority queue** from `docs/SYSTEM-INTEL.md`:
   - Look for `## PRIORITY QUEUE` section (active work)
   - Look for `## PARKED QUEUE` section (future features)

2. **Also check for feature requests** in dev_queue table:
   ```bash
   npx supabase db execute --linked -c "SELECT id, title, description, reported_by, priority, status, reported_at FROM dev_queue WHERE type = 'feature' AND status NOT IN ('closed') ORDER BY priority ASC, reported_at ASC"
   ```

3. **Display combined view:**
   - Active priorities from SYSTEM-INTEL.md (numbered, with [x] for done, [ ] for pending)
   - New feature requests from dev_queue (not yet in SYSTEM-INTEL)
   - Parked queue items (for future consideration)

4. **When user picks a feature:**
   - Create plan file: `docs/[feature]-plan.md`
   - Follow BUILD PROTOCOL from CLAUDE.md
   - Update SYSTEM-INTEL.md when complete

5. **When feature is built:**
   - Mark [x] in SYSTEM-INTEL.md priority queue
   - Update feature status in dev_queue: `{status: "ready_to_test"}`
   - [READY] notification auto-posts to Slack

## Output Format

```
## Feature Queue

### PRIORITY QUEUE (Active)
19. [ ] **Email Sequences** - Plan: docs/email-sequences-plan.md
20. [ ] **Call Analytics Deep** - Plan: docs/call-analytics-plan.md

### NEW REQUESTS (From Users)
- #7: "Add dark mode" - From: michael@... - Requested: Jan 19

### PARKED (Future)
- Push Notifications (2-4 hours, High value)
- AI Call Scoring (1 week, High value)
- Deal Intelligence (1-2 weeks, High value)

---
Which feature do you want to work on?
```

## Adding New Features

When user requests a feature via app/Slack:
1. It goes to dev_queue table
2. Shows up in "NEW REQUESTS" section above
3. When ready to build, add to SYSTEM-INTEL.md PRIORITY QUEUE
4. Create plan file and follow BUILD PROTOCOL