featureroadmaplisted

# /feature roadmap ## Instructions ### 1. Find the feature - List feature plans in `agents/features/`. - Also check module-level feature dirs via `enumerate_modules()` — for each module, look in `{module_path}/{modules.agent_folder}/features/` (Laravel shape: `app/Modules/*/agents/features/`). If the user specified a feature name, load it directly. Otherwise show a list and ask: ``` 📂 Feature plans: # Name Status ─ ────────────────────────────── ────── 1 import-csv-validation.md 📋 Planned 2 webhook-retry-logic.md 📋 Planned Which feature should get a roadmap? ``` If no features exist or all are `💡 Idea`: ``` ⚠️ No feature ready for a roadmap. Create a plan first with /feature-plan or refine with /feature-refactor. ``` Stop. ### 2. Analyze the feature - Read the feature file completely. - Read the roadmap template at `.augment/templates/roadmaps.md` for the structure. - Research the codebase for affected areas mentioned in the feature. Determine how many roadmaps are needed: - **Single roadmap:** Small/medium features that fit in one document. - **Multiple roadmaps:** Large features that span multiple phases or modules. ``` I've analyzed the feature: 📄 {feature title} 📐 Scope: {scope summary} 🔧 Affected areas: {modules, models, services} ─────────────────────────────────────────────── ROADMAP PROPOSAL: ─────────────────────────────────────────────── {Option A: Single roadmap} 📄 agents/