featuredevlisted

# /feature:dev > Full 7-phase feature development workflow for complex features. ## Trigger `/feature:dev {description}` or `/feature:dev` (interactive) ## When to use - New features that touch multiple files or modules - Features requiring architecture decisions - Complex integrations with existing code - Features where requirements are unclear Do NOT use for single-line fixes, trivial changes, or urgent hotfixes. ## Workflow ### Phase 1: Discovery 1. If no description provided, ask: "What feature do you want to build?" 2. Clarify the feature request: - What problem does it solve? - Who benefits? - What are the constraints? 3. Summarize understanding and **confirm with the user** before proceeding. ### Phase 2: Codebase Exploration 1. Use `codebase-retrieval` to find: - Similar features already implemented - Architecture patterns in the affected area - Key files, services, models, routes involved 2. Read identified files to build deep understanding. 3. Check module docs via `enumerate_modules()` — for each module, look in `{module_path}/{modules.agent_folder}/` (Laravel shape: `app/Modules/*/agents/`) if applicable. 4. Check existing contexts (`agents/settings/contexts/`) for the affected area. 5. Present findings with file references. ### Phase 3: Clarifying Questions 1. Review codebase findings against the feature request. 2. Identify underspecified aspects: - Edge cases and error handling - Integration points with existing code - Ba