mission-brief

# /mission-brief - Feature Planning

Turn an exploration report into an executable feature with tasks. HOUSTON reviews the exploration, convenes a planning council for input, then synthesizes everything into a plan for user approval.

**Hierarchy:**
- Project = the codebase (one per installation)
- Feature = scope of work (designed in /exploration)
- Tasks = implementation units (created here)

## The Process

1. **Check exploration folder** - list available reports in `.space-agents/exploration/`
2. **Confirm with user** - "I found X. Is this what you want to plan?"
3. **Read and analyze** - HOUSTON reads the exploration report
4. **Ask to convene council** - "Ready to send out the planning council?"
5. **Spawn council** - 3 agents analyze in parallel
6. **Synthesize** - HOUSTON combines own analysis + council input
7. **Present stages** - user approves each stage
8. **Write plan** - Beads records + markdown file
9. **Handoff** - offer `/mission-go` to begin execution

## Step 1: Check What's Available

List exploration reports:
```
.space-agents/exploration/YYYY-MM-DD-*/exploration.md
```

Present to user:
```
Found exploration reports:
  [1] 2026-01-18-auth-system - "User authentication with JWT"
  [2] 2026-01-15-caching-layer - "Redis caching for API"

Which one should we plan? (or describe something new)
```

## Step 2: HOUSTON's Own Analysis

Before spawning agents, read the exploration report yourself. Form your own view on:
- How to break this into tasks
- What the dependencies might be
- Key implementation considerations

This gives you context to evaluate the council's input.

## Step 3: Convene the Council

After user confirms, ask before spawning:
```
Ready to convene the planning council? I'll send out three agents to analyze:
- Task Planner (feature/task structure)
- Sequencer (dependencies, execution order)
- Implementer (TDD task breakdown)

They'll report back while we continue talking. Proceed?
```

## The Council

The council are **advisors**, not