--- name: ecommerce-brief-preparation description: 'Turn a rough ecommerce request into a normalized implementation brief. Use for clarifying requirements, asking targeted questions, and creating .ai/STORE-BRIEF.md before code generation.' argument-hint: 'Describe the store idea, constraints, and anything you already know' --- # Ecommerce Brief Preparation ## When to use - Starting a new ecommerce project from a rough or incomplete idea. - Normalizing a user request before scaffolding code. - Creating a single source of truth for storefront, backend, admin panel, and design decisions. ## Goal - Ask only the high-impact questions that unblock architecture, UX, catalog, auth, cart, admin, integrations, and visual direction. - Convert the user's request into a structured file named .ai/STORE-BRIEF.md based on [STORE-BRIEF.md](./assets/store-brief-template.md). - Record explicit decisions, assumptions, and unresolved risks. ## Required workflow 1. Parse the initial user request. 2. Use [discovery question bank](./assets/discovery-question-bank.md) to ask only the questions that materially affect implementation. 3. Decide whether the target is monorepo or split repos. 4. Normalize the result into .ai/STORE-BRIEF.md. 5. If the project is split across repos, create a repo-local .ai/STORE-BRIEF.md for the current repo and document the counterpart repo responsibilities. 6. Do not scaffold application code in this step unless the user explicitly asks for both steps in one run. ## Output requirements for .ai/STORE-BRIEF.md - Project summary and business context. - Repo mode and delivery assumptions. - Storefront scope. - Admin panel or back office scope. - Auth and cart decisions. - Data model outline. - Integrations. - Visual direction and asset status. - Development questions answered. - Assumptions and open risks. - AGENTS.md creation plan. - Implementation phases for the build step. ## References - [discovery question bank](./assets/discovery-question-bank.md) - [STORE-BRIEF template](./assets/store-brief-template.md)