---
description: Implement a new feature end-to-end (route, controller/service, view, test) following project conventions.
argument-hint: <description of the feature>
---

Implement this feature in the Mediknode/Unified codebase: **$ARGUMENTS**

Workflow:
1. Clarify the target: which subdomain (frontend public vs backend admin) and which instance(s) (all or a specific client)? If genuinely ambiguous, ask one question; otherwise pick the obvious option and state it.
2. Delegate the implementation to the `laravel-feature` agent (or `livewire-expert` if the UI is reactive). Reuse existing services/patterns — no new patterns where one exists.
3. Add a named route in the correct subdomain group.
4. Require a Feature test from the `test-writer` agent (RefreshDatabase, config-built URL, Spatie permissions, French test names). Include unauthorized + unauthenticated cases.
5. Run `vendor/bin/pint` on touched files and `php artisan test --filter` on the new test.

Report: files changed, route name(s), and test result.