Coordination Setup

## Setup: Track this exercise with Beads

```bash
bd create "Praxis: Set up Beads coordination for [project]" --type=feature --labels=learn,agents
bd create "Initialize .beads/ directory with bd init" --type=task --labels=learn
bd create "Create 3+ issues with proper labels and priority" --type=task --labels=learn
bd create "Establish dependency graph with bd dep add" --type=task --labels=learn
bd create "Test bd ready to verify unblocked work surfaces" --type=task --labels=learn
bd create "Document claim pattern for your workflow" --type=task --labels=learn
```

---

Help me set up MY work coordination system using Beads for [PROJECT_NAME].

I'm building MY approach to agent-native task management. Guide me through:

1. **Initialize Beads**:
   - Run `bd init` to create .beads/ directory
   - Configure labels for MY domains and types
   - Set up priority model (P0-P4 or custom)

2. **Create initial issues**:
   Create 3-5 issues that represent real work in [PROJECT_NAME]:
   ```bash
   bd create "[task title]" --type=task|feature|bug --priority=P2 --labels=[domain]
   ```

3. **Establish dependencies**:
   - Which issues block others?
   - Create the dependency graph:
   ```bash
   bd dep add [blocker-id] blocks [blocked-id]
   ```

4. **Test the workflow**:
   - Run `bd ready` to see unblocked work
   - Run `bd blocked` to verify dependencies work
   - Claim an issue: `bd update [id] --status=in_progress`

5. **Document MY coordination patterns**:
   - What labels do I use and why?
   - When do I create dependencies vs. leave issues independent?
   - What's my claim-and-complete workflow?

Project: [YOUR_PROJECT_NAME]
Domains/labels I use: [YOUR_LABELS]