contextcreatelisted

# /context create ## Instructions ### 1. Ask what to document If the user provided a topic, use it. Otherwise ask: ``` 📄 What area do you want to document? Examples: - A module (e.g. "ClientSoftware Module") - A service (e.g. "CustomerService and Tenant-Switching") - An integration (e.g. "ProBauS API Integration") - A domain area (e.g. "Import pipeline from upload to processing") - Infrastructure (e.g. "Queue system with Horizon") ``` ### 2. Determine scope (module vs. project-wide) Resolve module roots via `scripts/_lib/agent_settings.py::enumerate_modules()` (reads `modules.root_paths` + `modules.agent_folder` from `.agent-project-settings.yml`). If at least one module is discovered, ask: ``` Should the context be created in a module or in the project root? 1. 📦 In a module → {module_root}/{Module}/{agent_folder}/settings/contexts/ 2. 🌐 Project root → agents/settings/contexts/ ``` If module: - Render the list of modules from `enumerate_modules()` and ask which one. - Target: `{module_root}/{Module}/{agent_folder}/settings/contexts/` (Laravel example: `app/Modules/{Module}/agents/settings/contexts/`) - Create directory if it doesn't exist. If project-wide: - Target: `agents/settings/contexts/` ### 3. Determine context type ``` What type of context is this? 1. 📦 Module — structure and purpose of a module 2. 🏢 Domain — business logic across multiple modules 3. ⚙️ Service — complex service with dependencies 4. 🔗 Integration — external API/system integration