Feature Team

# Feature Development Team

Spawn an agent team for multi-file feature implementation with file ownership boundaries.

## Usage

/feature-team [feature description]

## When to Use
- Feature touches 3+ files across different modules
- Work can be split by module ownership (TIC, TSR, evaluation, tests, etc.)
- You want quality gate hooks to fire on each teammate's work

## Team Structure

The lead analyzes the feature and spawns teammates based on which modules are affected:

### Typical Roles

| Role | Owns | Agent Model |
|------|------|-------------|
| TIC implementer | `src/tic/` files (one teammate only) | Sonnet |
| TSR implementer | `src/tsr/` files | Sonnet |
| Eval implementer | `evaluation/bloom_eval_v2/` files | Sonnet |
| Test writer | `tests/test_*.py` files (one per test file) | Sonnet |
| Script writer | `scripts/*.py` files | Sonnet |

### File Ownership Rules (from .claude/rules/agent-teams.md)
- TIC checker, enforcement, contracts: ONE teammate only
- Evaluation graders, reporters: ONE teammate only
- Scenarios, tests, scripts, metrics: one per FILE is safe
- Safety-critical zones require plan approval from lead

## Lead Behavior
1. **Plan the feature** — identify all files that need to change
2. **Break into tasks** — 5-6 tasks per teammate, each producing a clear deliverable
3. **Assign ownership** — each teammate gets a non-overlapping set of files
4. **Set dependencies** — implementation before tests, shared utilities before consumers
5. **Use delegate mode** — coordinate, don't implement
6. **Require plan approval** for safety-critical zones:
   - `configs/contracts/*.yaml`
   - `src/tic/events.py`
   - `evaluation/bloom_eval_v2/scenarios/`
   - `evaluation/bloom_eval_v2/graders/`

## Example Spawn

Create an agent team to add the new "medication interaction" scenario type.

Teammates:

• "scenario-dev" (Sonnet): Create evaluation/bloom_eval_v2/scenarios/templates/domain_medication_interactions.py following the pattern in domain_cardiovascular.py. Also create the scenario loader integration. Require plan approval (this is a safety-critical zone).
• "contract-dev" (Sonnet): Add medication_safety_v2.yaml contract in configs/contracts/ with interaction-specific states and transitions. Require plan approval.
• "test-writer" (Sonnet): Write tests/test_medication_scenarios.py and tests/test_medication_contract.py. Blocked until scenario-dev and contract-dev finish.
• "docs-updater" (Sonnet): Update docs/DOCUMENTATION_AUDIT.md, skills/INDEX.md, and any relevant READMEs. Blocked until all implementation is done.

Use delegate mode. Break each role into 5-6 concrete tasks.

## Quality Gates
All teammates are subject to hooks:
- **TeammateIdle:** lint, PHI detection, contract validation, protected file guard
- **TaskCompleted:** targeted tests for modified modules, determinism checks, format verification

If a hook rejects work, the teammate must fix the issue before proceeding.

## After Completion
1. Lead runs full test suite: `pytest tests/ -v`
2. Lead runs lint: `ruff check . && ruff format .`
3. Lead verifies no PHI: `python scripts/detect_phi.py --strict`
4. Commit with appropriate prefix: `feat:`, `fix:`, etc.