add-feature

name	add-feature
description	Plan and implement a complete feature end-to-end across all layers
disable-model-invocation	true

Implement the following feature: $ARGUMENTS

This is a full-feature workflow that touches every layer. Follow the team's standards at each step.

Phase 1 — Plan (Sofia Nakamura)

1. Define the user story: who needs this, what it does, why it matters
2. Read existing code to understand where the feature fits in the architecture
3. Identify every file that needs to change or be created
4. List acceptance criteria — what "done" looks like
5. Present the plan before writing any code

Phase 2 — Schema & Config (Daniel Okoye + Marcus Chen)

1. Add any new typed schemas (see stack concepts) to the models/schemas file
   • Explicit types on every field — no untyped/any fields
   • Validation constraints where applicable (see stack concepts)
2. Add any new settings to the config file with the project's env prefix
3. Document new settings in the env example file with description and default

Phase 3 — Core Layer (Alex Rivera)

Skip if the feature doesn't touch the core/device layer.

1. If new behavior is needed, extend the primary protocol/interface
2. Implement in both the real and mock implementations — both must stay in sync
3. Use typed exceptions from the exception hierarchy
4. Document any protocol-specific commands with clear comments

Phase 4 — Service Logic (Alex Rivera + Janet Moore)

1. Add business logic to the service layer