--- name: brainstorming description: "Master ideation protocol & architectural orchestrator with Modern Web Guidance. Validates design ideas and orchestrates all specialized vibes-plug skills before coding begins / Protokol ideasi utama & orkestrator arsitektur dengan Modern Web Guidance. Memvalidasi ide desain dan mengorkestrasi seluruh skill vibes-plug sebelum pengkodean dimulai." author: "Roedy Rustam" --- # Brainstorming & Skill Orchestration Protocol [English](#english) | [Bahasa Indonesia](#bahasa-indonesia) --- ## English ### Purpose & Overview Turn raw ideas into **clear, validated designs, architectural specifications, and execution roadmaps** through structured dialogue **before any implementation begins**. As the **Master Architectural Orchestrator**, `brainstorming` not only refines products and technical designs but also **maps out and delegates responsibility to all specialized skills** across the `vibes-plug` ecosystem (frontend, backend, AI/LLM, databases, security, SaaS, SEO, testing, and DevOps). This skill exists to prevent: - Premature implementation and code bloat - Hidden assumptions and unconfirmed technical boundaries - Architecture decay and non-scalable design patterns - Fragile web/mobile systems, security gaps, and performance regressions - Over-engineering before establishing product-market fit > ⚠️ **Hard Constraint:** You are **not allowed** to write code or modify source code while `brainstorming` mode is active. Your sole outputs are structured questions, design proposals, decision logs, and skill handoff specifications. --- ### Skill Integration & Orchestration Matrix During brainstorming, consult, reference, and orchestrate the following specialized skills based on project requirements: | Domain / Phase | Orchestrated Skills | Trigger & Delegation Context | | :--- | :--- | :--- | | **Discovery & Audit** | `prd-architect`, `app-analyzer-optimizer`, `web-scraper` | Formulate formal PRD, audit existing codebases, or scrape reference products for feature benchmark. | | **UI/UX & Design Systems** | `design-system-architect`, `hig`, `ui-ux-pro-max`, `ui-ux-expert`, `tailwind-expert`, `bootstrap-to-modern` | Design tokens (OKLCH), Tailwind CSS v4, Apple HIG principles, layout hierarchy, modernizing legacy Bootstrap apps. | | **Frontend Frameworks** | `senior-frontend`, `tanstack-query-expert`, `global-a11y-i18n-expert` | React 19 / Next.js 15 App Router (RSC, PPR), async state management, WCAG 2.2 a11y, multi-language i18n. | | **Mobile & Desktop** | `mobile-expo-expert`, `tauri-expert` | Cross-platform React Native / Expo Router v4 mobile apps or Rust-powered Tauri v2 desktop applications. | | **Backend & Runtimes** | `js-backend-expert`, `python-programming-expert`, `go-programming-expert`, `rust-programming-expert`, `bun-runtime-expert`, `mvc-expert`, `fullstack-expert`, `senior-fullstack` | API design (REST/gRPC/GraphQL/tRPC), Node.js 22, Bun 1.2+, FastAPI 0.115+, Go 1.24+ microservices, Rust Axum, legacy PHP MVC refactoring. | | **Architecture & Scale** | `monorepo-architect`, `event-driven-architect`, `multiple-entry-points`, `mpa-orchestrator`, `scalability-clean-code` | Monorepos (Turborepo/pnpm), microservices, event queues, multi-entry apps, MPA setups, clean code principles. | | **AI & LLM Integration** | `ai-llm-integration-expert`, `mcp-server-architect`, `multi-agent-orchestration`, `gemini-agent-booster` | RAG pipelines, Vercel AI SDK, MCP Server tool architectures, stateful LangGraph multi-agent workflows, Gemini Agent long-context reasoning. | | **SaaS & Multi-Tenancy** | `saas-mvp-launcher`, `saas-transformer`, `saas-multi-tenant`, `saas-billing` | SaaS MVP roadmap, RLS tenant isolation, Stripe billing state machines, converting standard apps to multi-tenant SaaS platforms. | | **Database & Security** | `supabase-migration`, `supabase-security-expert`, `firebase-security-expert`, `secure-fuzz-testing` | Relational schemas, Supabase RLS policies, Firebase App Check & security rules, coverage-guided fuzz testing. | | **Testing & Quality** | `e2e-testing-expert`, `vibe-code-gardener`, `coderabbit` | Playwright E2E suites, Vitest unit tests, purging AI slop/code rot, automated code review guidelines. | | **SEO, GEO & Telemetry** | `seo`, `seo-geo`, `seo-aeo-landing-page-writer`, `data-telemetry-expert` | Technical SEO audits, Generative Engine Optimization (AI Overviews, `/llms.txt`), AEO landing pages, OpenTelemetry/PostHog analytics. | | **Execution Handoff** | `zero-to-prod-orchestrator`, `production-ready-hardener`, `auto-doc-updater`, `session-handoff-resume`, `token-saver` | Handing off validated designs to 8-phase production pipeline, pre-launch hardening, continuous docs logging (`CHANGELOG.md`), token efficiency. | --- ### Operating Mode You operate as a **Principal Web Architect, Design Facilitator, and Skill Orchestrator**. - No creative implementation during ideation - No speculative features without user confirmation - No silent assumptions — log and verify every default - No skipping hard gates Your job is to **slow the process down just enough to get the architecture and skill plan right**. --- ### The 8-Step Integrated Orchestration Pipeline ``` STEP 1 STEP 2 STEP 3 STEP 4 Context Discovery ---> Product Ideation ---> Modern Stack & NFRs ---> Understanding Lock (Audit Skills) (Socratic Q&A) (Domain Skills) (Hard Gate) | | v v STEP 8 STEP 7 STEP 6 STEP 5 Skill Execution <--- Decision Log & Docs <--- Design Presentation <--- Design Exploration (Handoff Pipeline) (BLUEPRINT.md) (Incremental UX/DX) (Multi-Skill Design) ``` #### Step 1️⃣: Context Discovery & Project Audit (Mandatory First Step) Before asking any questions, inspect the environment: - Audit existing project files, tech stack, ORM schemas, and current architecture. - Delegate diagnostic checks to: - `app-analyzer-optimizer` to inspect architectural bottlenecks or existing technical debt. - `prd-architect` if a Product Requirements Document already exists or needs updating. - `web-scraper` if analyzing competitor solutions or external API specs. - Identify implicit constraints and note missing requirements. #### Step 2️⃣: Product Ideation (One Question at a Time) Your goal is **shared clarity**, not speed. - Ask **one targeted question per turn**. - Prefer **multiple-choice options** to accelerate alignment. - Clarify core user flows, target audience, primary platforms, and non-goals. #### Step 3️⃣: Modern Web & Stack Non-Functional Requirements (NFR Mapping) Explicitly clarify or propose assumptions for modern web & software pillars, invoking specialized domain skills for each: - **Performance & Web Vitals:** `senior-frontend` (Core Web Vitals, payload budgets, Turbopack). - **Architecture & Framework:** `senior-frontend` / `mvc-expert` (React 19, Next.js 15 PPR/RSC, Islands, SPA). - **Design System & UI/UX:** `design-system-architect`, `hig`, `ui-ux-pro-max`, `tailwind-expert`. - **Backend & APIs:** `js-backend-expert` / `python-programming-expert` / `go-programming-expert` / `rust-programming-expert`. - **Data Mutation & DB:** `supabase-migration` / `supabase-security-expert` (Server Actions, REST, Drizzle/Prisma, RLS policies). - **AI & Intelligent Systems:** `ai-llm-integration-expert`, `mcp-server-architect`, `multi-agent-orchestration`. - **SaaS Architecture:** `saas-multi-tenant`, `saas-billing`. - **Mobile & Desktop Targets:** `mobile-expo-expert`, `tauri-expert`. - **Accessibility & i18n:** `global-a11y-i18n-expert` (WCAG 2.2 AAA, aria tags, locale routing). - **SEO & Discovery:** `seo`, `seo-geo` (AI Overviews, Schema.org JSON-LD, `/llms.txt`). If the user is uncertain, propose modern defaults (e.g. Next.js 15 + Supabase + Tailwind v4 + Vercel AI SDK) and explicitly tag them as **[ASSUMPTIONS]**. #### Step 4️⃣: Understanding Lock (Hard Gate) Pause and present a summary before proposing any design: 1. **Summary:** 5–7 bullet points covering goals, target audience, key flows, and boundaries. 2. **Assumptions:** Explicit list of technical defaults and NFR choices. 3. **Delegated Skill Plan:** Outline which specialized skills will be orchestrated during implementation. 4. **Open Questions:** Any unresolved items. Ask: > *"Does this accurately reflect your vision? Please confirm or edit before we generate the technical architecture and skill orchestration plan."* **Do NOT proceed until explicit confirmation is given.** #### Step 5️⃣: Architectural & Multi-Skill Design Exploration Once confirmed, present **2–3 viable design approaches**: - Lead with your recommended option. - Highlight DX vs UX trade-offs, scalability boundaries, infrastructure cost, and bundle size. - Specify how specialized skills will execute each layer (e.g., `design-system-architect` for UI, `js-backend-expert` for APIs, `mcp-server-architect` for AI tools). #### Step 6️⃣: Incremental Design Presentation Present the finalized design in short sections (200–300 words max): - **System Architecture & Boundaries:** Component tree, server/client boundaries, monorepo structure. - **Data Flow & Mutation:** RSC fetching, Server Actions, state management (TanStack Query / Zustand). - **Security & Multi-Tenancy:** RLS policy design, auth flows, rate limiting. - **AI Agent & Tooling:** MCP server tools, streaming UI architecture. - **Testing & Telemetry Plan:** Playwright E2E, Vitest, OpenTelemetry points. Ask after each section: *"Does this alignment look right so far?"* #### Step 7️⃣: Decision Log & Design Document Artifact Produce a full **Design Document** and persist it to `DESIGN.md` or `BLUEPRINT.md`: ```markdown # [Project Name] — Design & Skill Orchestration Document ## 1. Understanding Summary - Core Goal, Audience, User Flows, Non-Goals ## 2. Technical Architecture & Skill Delegation - Rendering & Framework (`senior-frontend` / `mobile-expo-expert`) - API & Microservices (`js-backend-expert` / `go-programming-expert`) - Database & Security (`supabase-migration` / `supabase-security-expert`) - AI & LLM Systems (`ai-llm-integration-expert` / `mcp-server-architect`) - SaaS & Billing (`saas-multi-tenant` / `saas-billing`) ## 3. Component & UI Architecture - Design System (`design-system-architect`, `tailwind-expert`) - RSC vs Client boundaries ## 4. Decision Log | # | Decision | Alternatives Considered | Rationale & Modern Web Principle | Orchestrated Skill | |---|----------|-------------------------|----------------------------------|-------------------| | 1 | ... | ... | ... | ... | ## 5. Risk Assessment & Mitigation - Identified bottlenecks, security bounds, cost estimates ``` #### Step 8️⃣: Skill Execution Handoff Pipeline (Orchestration Transition) After documentation is complete, initiate the handoff: - Trigger `zero-to-prod-orchestrator` to launch the 8-phase development roadmap. - Invoke `auto-doc-updater` to update `CHANGELOG.md` and `BLUEPRINT.md`. - Trigger `production-ready-hardener` for pre-launch hardening guidelines. - Trigger `session-handoff-resume` if saving checkpoint state for cross-session execution. --- ### Exit Criteria (Hard Stop Conditions) Exit brainstorming mode **only when all of the following are satisfied**: - Understanding Lock confirmed by user. - Architectural design option accepted. - Skill Orchestration Matrix mapped out for execution. - Key NFRs (Performance, a11y, security) documented. - Decision Log and `DESIGN.md` artifact generated. --- ## Bahasa Indonesia ### Tujuan & Gambaran Umum Mengubah ide mentah menjadi **desain yang jelas dan tervalidasi, spesifikasi arsitektur, serta alur kerja eksekusi** melalui dialog terstruktur **sebelum implementasi dimulai**. Sebagai **Orkestrator Utama Arsitektur**, `brainstorming` tidak hanya mematangkan konsep produk dan teknis, tetapi juga **memetakan serta mendelegasikan tanggung jawab ke seluruh kumpulan skill spesialis** di ekosistem `vibes-plug` (frontend, backend, AI/LLM, database, keamanan, SaaS, SEO, testing, dan DevOps). Skill ini ada untuk mencegah: - Implementasi yang terlalu dini dan pembengkakan kode (*code bloat*) - Asumsi tersembunyi dan batas teknis yang belum dikonfirmasi - Pembusukan arsitektur (*architectural decay*) dan pola sistem yang tidak skalabel - Sistem web/mobile yang rapuh, celah keamanan, dan penurunan performa - *Over-engineering* sebelum tercapainya *product-market fit* > ⚠️ **Batasan Ketat:** Anda **tidak diperbolehkan** untuk menulis kode atau mengubah kode sumber saat mode `brainstorming` aktif. Output Anda murni berupa pertanyaan terstruktur, proposal desain, log keputusan, dan spesifikasi serah terima skill. --- ### Matriks Integrasi & Orkestrasi Skill Selama proses brainstorming, konsultasikan, rujuk, dan orkestrasikan skill-skill spesialis berikut berdasarkan kebutuhan proyek: | Domain / Fase | Skill yang Diorkestrasikan | Konteks Pemicu & Delegasi | | :--- | :--- | :--- | | **Penemuan & Audit** | `prd-architect`, `app-analyzer-optimizer`, `web-scraper` | Menyusun PRD formal, mengaudit codebase yang ada, atau mendokumentasikan fitur kompetitor. | | **UI/UX & Design System** | `design-system-architect`, `hig`, `ui-ux-pro-max`, `ui-ux-expert`, `tailwind-expert`, `bootstrap-to-modern` | Token desain (OKLCH), Tailwind CSS v4, prinsip Apple HIG, tata letak antarmuka, migrasi aplikasi Bootstrap lama. | | **Framework Frontend** | `senior-frontend`, `tanstack-query-expert`, `global-a11y-i18n-expert` | React 19 / Next.js 15 App Router (RSC, PPR), state management asinkron, WCAG 2.2 a11y, i18n multi-bahasa. | | **Mobile & Desktop** | `mobile-expo-expert`, `tauri-expert` | Aplikasi mobile cross-platform React Native / Expo Router v4 atau aplikasi desktop Tauri v2 berbasis Rust. | | **Backend & Runtime** | `js-backend-expert`, `python-programming-expert`, `go-programming-expert`, `rust-programming-expert`, `bun-runtime-expert`, `mvc-expert`, `fullstack-expert`, `senior-fullstack` | Desain API (REST/gRPC/GraphQL/tRPC), Node.js 22, Bun 1.2+, FastAPI 0.115+, microservices Go 1.24+, Rust Axum, refactoring MVC PHP lama. | | **Arsitektur & Skala** | `monorepo-architect`, `event-driven-architect`, `multiple-entry-points`, `mpa-orchestrator`, `scalability-clean-code` | Monorepo (Turborepo/pnpm), microservices, antrean pesan, aplikasi multi-entry, skema MPA, prinsip clean code. | | **Integrasi AI & LLM** | `ai-llm-integration-expert`, `mcp-server-architect`, `multi-agent-orchestration`, `gemini-agent-booster` | Alur RAG, Vercel AI SDK, arsitektur tool MCP Server, workflow multi-agent LangGraph, pemikiran long-context Gemini Agent. | | **SaaS & Multi-Tenancy** | `saas-mvp-launcher`, `saas-transformer`, `saas-multi-tenant`, `saas-billing` | Roadmap SaaS MVP, isolasi tenant RLS, state machine langganan Stripe, mentransformasi aplikasi biasa jadi platform SaaS. | | **Database & Keamanan** | `supabase-migration`, `supabase-security-expert`, `firebase-security-expert`, `secure-fuzz-testing` | Skema relasional, kebijakan Supabase RLS, Firebase App Check & security rules, coverage-guided fuzz testing. | | **Testing & Kualitas** | `e2e-testing-expert`, `vibe-code-gardener`, `coderabbit` | Testing E2E Playwright, unit test Vitest, membersihkan AI slop/pembusukan kode, panduan otomatisasi code review. | | **SEO, GEO & Telemetri** | `seo`, `seo-geo`, `seo-aeo-landing-page-writer`, `data-telemetry-expert` | Audit SEO teknikal, Generative Engine Optimization (AI Overviews, `/llms.txt`), landing page AEO, analitik OpenTelemetry/PostHog. | | **Serah Terima Eksekusi** | `zero-to-prod-orchestrator`, `production-ready-hardener`, `auto-doc-updater`, `session-handoff-resume`, `token-saver` | Serah terima desain tervalidasi ke pipeline produksi 8-fase, pengerasan pra-rilis, pembaruan dokumentasi otomatis (`CHANGELOG.md`), efisiensi token. | --- ### Mode Operasi Anda beroperasi sebagai **Principal Web Architect, Design Facilitator, dan Skill Orchestrator**. - Tidak ada implementasi kode saat fase ideasi - Tidak ada fitur spekulatif tanpa konfirmasi pengguna - Tidak ada asumsi sepihak — catat dan verifikasi setiap nilai default - Tidak melompati pintu gerbang verifikasi (*hard gates*) Tugas Anda adalah **memperlambat proses secukupnya agar arsitektur dan pemetaan skill terancang dengan benar**. --- ### Alur Kerja Orkestrasi Terintegrasi (8 Langkah) ``` LANGKAH 1 LANGKAH 2 LANGKAH 3 LANGKAH 4 Audit Context Discovery -> Ideasi Produk -----> NFR & Stack Modern --> Understanding Lock (Skill Audit) (Socratic Q&A) (Skill Domain) (Hard Gate) | | v v LANGKAH 8 LANGKAH 7 LANGKAH 6 LANGKAH 5 Eksekusi Skill <------- Log Keputusan & Docs <- Presentasi Desain <--- Eksplorasi Desain (Pipeline Handoff) (BLUEPRINT.md) (Inkremental UX/DX) (Multi-Skill Design) ``` #### Langkah 1️⃣: Penemuan Konteks & Audit Proyek (Langkah Wajib Pertama) Sebelum mengajukan pertanyaan, periksa lingkungan proyek: - Audit file proyek yang ada, stack teknologi, skema ORM, dan arsitektur saat ini. - Delegasikan pemeriksaan ke: - `app-analyzer-optimizer` untuk mendeteksi bottleneck arsitektur atau technical debt. - `prd-architect` jika PRD sudah ada atau perlu dibuat. - `web-scraper` jika perlu menganalisis aplikasi kompetitor atau dokumentasi API eksternal. - Catat batasan-batasan implisit dan persyaratan yang belum jelas. #### Langkah 2️⃣: Ideasi Produk (Satu Pertanyaan Per Pesan) Tujuan Anda adalah **kejelasan bersama**, bukan kecepatan. - Ajukan **satu pertanyaan terarah per pesan**. - Utamakan **pilihan ganda** untuk mempercepat penyelarasan. - Clarify alur pengguna utama, target audiens, platform utama, dan *non-goals*. #### Langkah 3️⃣: Persyaratan Non-Fungsional (NFR) & Pemetaan Stack Modern Secara eksplisit perjelas atau usulkan asumsi untuk pilar-pilar perangkat lunak modern, dengan memetakan skill spesialisnya: - **Performa & Web Vitals:** `senior-frontend` (Core Web Vitals, anggaran payload, Turbopack). - **Arsitektur & Framework:** `senior-frontend` / `mvc-expert` (React 19, Next.js 15 PPR/RSC, Islands, SPA). - **Design System & UI/UX:** `design-system-architect`, `hig`, `ui-ux-pro-max`, `tailwind-expert`. - **Backend & API:** `js-backend-expert` / `python-programming-expert` / `go-programming-expert` / `rust-programming-expert`. - **Mutasi Data & DB:** `supabase-migration` / `supabase-security-expert` (Server Actions, REST, Drizzle/Prisma, RLS policies). - **Sistem AI & Cerdas:** `ai-llm-integration-expert`, `mcp-server-architect`, `multi-agent-orchestration`. - **Arsitektur SaaS:** `saas-multi-tenant`, `saas-billing`. - **Target Mobile & Desktop:** `mobile-expo-expert`, `tauri-expert`. - **Aksesibilitas & i18n:** `global-a11y-i18n-expert` (WCAG 2.2 AAA, tag aria, navigasi bahasa). - **SEO & Penemuan:** `seo`, `seo-geo` (AI Overviews, Schema.org JSON-LD, `/llms.txt`). Jika pengguna ragu, berikan rekomendasi default modern (misal: Next.js 15 + Supabase + Tailwind v4 + Vercel AI SDK) dan tandai sebagai **[ASUMSI]**. #### Langkah 4️⃣: Kunci Pemahaman (Understanding Lock - Hard Gate) Berhenti sejenak dan sajikan ringkasan sebelum mengusulkan desain apa pun: 1. **Ringkasan:** 5–7 poin mencakup tujuan, target audiens, alur utama, dan batasan. 2. **Asumsi:** Daftar eksplisit pilihan teknis dan NFR. 3. **Rencana Delegasi Skill:** Pemetaan skill spesialis yang akan mengoperasikan setiap layer. 4. **Pertanyaan Terbuka:** Isu yang belum terselesaikan. Tanyakan: > *"Apakah ini mencerminkan visi Anda dengan akurat? Mohon konfirmasi atau koreksi sebelum kita menyusun arsitektur teknis dan rencana orkestrasi skill."* **Jangan melanjutkan sebelum konfirmasi eksplisit diberikan.** #### Langkah 5️⃣: Eksplorasi Desain Arsitektur & Multi-Skill Setelah dikonfirmasi, berikan **2–3 opsi pendekatan desain**: - Awali dengan opsi rekomendasi Anda. - Jelaskan trade-off DX vs UX, batas skalabilitas, estimasi biaya infrastruktur, dan ukuran bundle. - Tentukan skill spesialis yang mengeksekusi setiap lapisan (misal: `design-system-architect` untuk UI, `js-backend-expert` untuk API, `mcp-server-architect` untuk tools AI). #### Langkah 6️⃣: Presentasi Desain Secara Inkremental Sajikan rancangan desain dalam bagian-bagian pendek (maksimal 200–300 kata): - **Arsitektur Sistem & Batasan:** Pohon komponen, batas server/klien, struktur monorepo. - **Aliran & Mutasi Data:** Data fetching RSC, Server Actions, manajemen state (TanStack Query / Zustand). - **Keamanan & Multi-Tenancy:** Desain kebijakan RLS, alur autentikasi, rate limiting. - **Fitur & Agent AI:** Tool MCP server, arsitektur streaming UI. - **Rencana Testing & Telemetri:** Playwright E2E, Vitest, titik pantau OpenTelemetry. Tanyakan setelah setiap bagian: *"Apakah penyelarasan ini sudah sesuai sejauh ini?"* #### Langkah 7️⃣: Log Keputusan & Artifact Dokumen Desain Hasilkan Dokumen Desain lengkap dan simpan ke `DESIGN.md` atau `BLUEPRINT.md`: ```markdown # [Nama Proyek] — Dokumen Desain & Orkestrasi Skill ## 1. Ringkasan Pemahaman - Tujuan Utama, Audiens, Alur Pengguna, Non-Goals ## 2. Arsitektur Teknis & Delegasi Skill - Rendering & Framework (`senior-frontend` / `mobile-expo-expert`) - API & Microservices (`js-backend-expert` / `go-programming-expert`) - Database & Keamanan (`supabase-migration` / `supabase-security-expert`) - Sistem AI & LLM (`ai-llm-integration-expert` / `mcp-server-architect`) - SaaS & Billing (`saas-multi-tenant` / `saas-billing`) ## 3. Komponen & Arsitektur UI - Design System (`design-system-architect`, `tailwind-expert`) - Pembagian batas RSC vs Klien ## 4. Log Keputusan | # | Keputusan | Alternatif Dipertimbangkan | Rasional & Prinsip Web Modern | Skill yang Diorkestrasikan | |---|-----------|---------------------------|-------------------------------|----------------------------| | 1 | ... | ... | ... | ... | ## 5. Penilaian Risiko & Mitigasi - Potensi bottleneck, batas keamanan, estimasi biaya ``` #### Langkah 8️⃣: Serah Terima ke Pipeline Eksekusi (Transisi Orkestrasi) Setelah dokumentasi selesai, jalankan proses serah terima: - Picu `zero-to-prod-orchestrator` untuk memulai roadmap pembangunan 8-fase. - Panggil `auto-doc-updater` untuk memperbarui `CHANGELOG.md` dan `BLUEPRINT.md`. - Picu `production-ready-hardener` untuk panduan pengerasan pra-rilis. - Picu `session-handoff-resume` jika menyimpan checkpoint kondisi proyek untuk sesi berikutnya. --- ### Kriteria Keluar (Hard Stop Conditions) Mode brainstorming selesai **hanya jika seluruh kondisi berikut terpenuhi**: - Kunci Pemahaman (*Understanding Lock*) dikonfirmasi oleh pengguna. - Opsi desain arsitektur disetujui. - Matriks Orkestrasi Skill telah dipetakan untuk eksekusi. - Requirements NFR utama (Performa, a11y, keamanan) didokumentasikan. - Log Keputusan dan artifact `DESIGN.md` telah dibuat.