create-vasvibe 0.2.2 → 1.0.0

package/template/README.md

@@ -3,32 +3,43 @@
 > _This README ships from the [`create-vasvibe`](https://www.npmjs.com/package/create-vasvibe) starter. Examples reference a boat tour booking project (Labuan Bajo) for illustration. Replace examples with your own context as needed._
 
 Selamat datang di ekosistem **Vibe Coding**.
-Ini adalah standar alur kerja pengembangan software berbasis **AI Agent** (GitHub Copilot + Claude Sonnet) yang mengutamakan struktur, dokumentasi otomatis, dan validasi berjenjang.
+Ini adalah standar alur kerja pengembangan software berbasis **AI Agent** yang mengutamakan struktur, dokumentasi otomatis, dan validasi berjenjang. 
+Template ini telah berevolusi dan secara *native* mendukung integrasi untuk berbagai AI agent environment mutakhir:
+- **Google Antigravity** (`.agents/`)
+- **Claude Code** (`.claude/`)
+- **OpenCode** (`.opencode/`)
+- **GitHub Copilot Workspace** (`.github/prompts/`)
+- Serta dilengkapi **Shared Agent Workflows** (`agent/workflows/`) sebagai *source of truth* agar perilaku agen konsisten di seluruh platform.
 
 ---
 
 ## ⚡ Quick start (untuk tim baru)
 
-Scaffold project baru lengkap dengan semua agent prompts, skills, dan struktur folder kerja standar tim:
+Gunakan *command* CLI resmi untuk melakukan scaffolding project baru. Proses ini akan meng-copy seluruh konfigurasi agent, prompt, skills, serta kerangka direktori standar tim ke project baru Anda:
 
 ```bash
+# Interaktif (akan ada pertanyaan)
 npx create-vasvibe my-new-project
+
+# Masuk ke direktori kerja
 cd my-new-project
 ```
 
-Yang akan ter-scaffold otomatis:
-- `.agents/`, `.claude/`, `.opencode/`, `.github/prompts/`, `agent/workflows/` — semua agent prompts & skills
-- `codes/`, `specifications/`, `tests/` — folder kerja dengan `.gitignore` rules
-- `project_overview_example.md`, `GIT_STRUCTURE_GUIDE.md`, `README.md`, `skills-lock.json`
-
-Flag yang tersedia:
-- `--yes` skip semua prompt
-- `--no-git` skip git init
-- `--no-claude` / `--no-opencode` / `--no-github` / `--no-workflows` untuk exclude toolchain tertentu
+**Struktur yang Ter-scaffold Otomatis:**
+- `codes/`, `specifications/`, `tests/` — folder kerja utama (telah dilindungi oleh aturan `.gitignore` agar tidak berantakan).
+- Kerangka prompt dari seluruh environment (`.agents`, `.claude`, `.opencode`, `.github`, `agent/workflows`).
+- File standard: `project_overview_example.md`, `GIT_STRUCTURE_GUIDE.md`, `skills-lock.json`.
 
-Source CLI: [`packages/create-vasvibe/`](./packages/create-vasvibe).
+**Opsi / Flag Tambahan:**
+| Flag | Deskripsi |
+|------|-----------|
+| `-y, --yes` | Skip semua pertanyaan (gunakan setting default) |
+| `--no-git` | Jangan jalankan `git init` secara otomatis |
+| `--no-opencode` | Abaikan folder `.opencode/` |
+| `--no-claude` | Abaikan folder `.claude/` dan `.agents/` |
+| `--no-github` | Abaikan folder `.github/prompts/` |
+| `--no-workflows` | Abaikan folder `agent/workflows/` |
 
----
 
 ## 🤖 Tentang AI Agent
 
@@ -50,6 +61,7 @@ Dalam workflow ini, kita menggunakan **8 AI Agent persona** yang bekerja secara
 3.  **Role Segregation:** Analis, Developer, dan QA adalah persona berbeda dengan tanggung jawab spesifik.
 4.  **Log Everything:** Setiap sesi coding dan testing dicatat untuk menjaga kontinuitas memori AI.
 5.  **Human-in-the-Loop:** Manusia sebagai Decision Maker, AI sebagai Executor.
+6.  **Git Branching & Repo Management:** Agent seperti Developer, Fixer, dan Tester dibekali pemahaman ketat mengenai *git branching* (membuat branch, pull/merge origin) untuk menjaga keutuhan `main`/`development` branch.
 
 ---
 
@@ -58,18 +70,23 @@ Workflow ini akan secara otomatis mengelola struktur folder berikut:
 
 ```text
 root/
-├── .github/
-│   └── prompts/              # [BRAIN] System Instructions untuk AI Agent
-│       ├── initiator.prompt.md      # Agent: Project Initiator
-│       ├── analyst.prompt.md        # Agent: System Analyst
-│       ├── developer.prompt.md      # Agent: Software Developer
-│       ├── fixer.prompt.md          # Agent: Bug Fixer & Debugger
-│       ├── developer.prompt.md       # Agent: Developer
-│       ├── tester.prompt.md         # Agent: QA Tester
-│       ├── fixer.prompt.md          # Agent: Bug Fixer
-│       ├── pm.prompt.md             # Agent: Project Manager ⭐ NEW
-│       ├── sysarch.prompt.md        # Agent: System Architect
-│       └── document.prompt.md       # Agent: Technical Writer
+├── .agents/                  # [BRAIN] Konfigurasi Google Antigravity & Skills
+│   ├── agents/               # Definisi persona agent (analyst, developer, tester, dll)
+│   └── skills/               # Folder berisi reusable tools/skills yang dapat diakses oleh agent
+│
+├── .claude/                  # [BRAIN] Konfigurasi & Prompt Claude Code
+│   └── agents/
+│
+├── .opencode/                # [BRAIN] Konfigurasi & Commands OpenCode
+│   └── commands/
+│
+├── .github/                  # [BRAIN] Konfigurasi GitHub Copilot Workspace
+│   └── prompts/
+│
+├── agent/workflows/          # [CORE] Source of Truth untuk semua instruksi agent
+│   ├── analyst.md
+│   ├── developer.md
+│   └── ... 
 │
 ├── project_overview.md       # [MASTER] Definisi produk, tech stack, & UI/UX
 │                             # 👤 HUMAN: Review & approve setelah Initiator Agent buat
@@ -78,43 +95,34 @@ root/
 │   ├── README.md            # Index semua spesifikasi
 │   ├── 000_spec_environment_setup.md # Infrastruktur (Wajib pertama)
 │   ├── 001_spec_database_schema.md
-│   ├── 002_spec_authentication.md
-│   ├── 003_spec_booking_management.md
 │   └── ...                  # 👤 HUMAN: Review setiap spec sebelum dev
 │
 ├── task/                     # [PROJECT MANAGEMENT] Output dari PM Agent ⭐ NEW
 │   ├── task_list.md         # Central task tracking (priority, status, dependencies)
-│   └── PROJECT_STATUS_REPORT.md # Progress reports
+│   ├── PROJECT_STATUS_REPORT.md # Progress reports
+│   ├── TASK-001/            # Folder khusus per task
+│   │   ├── plan.md          # Rencana kerja & log eksekusi task terkait
+│   │   └── ...
+│   └── TASK-002/            # Setiap task baru akan diisolasi ke dalam sub-folder tersendiri
 │
 ├── architecture/             # [INFRA] Output dari SysArch Agent
 │   ├── current_state.md     # Application analysis
 │   ├── server_specifications.md # Server specs (CPU, RAM, Storage)
-│   ├── deployment_plan.md   # Deployment strategy & steps
-│   ├── cost_analysis.md     # Infrastructure cost breakdown
-│   └── monitoring_plan.md   # Observability & alerting
+│   └── ...
 │
 ├── codes/                    # [SRC] Output dari Developer Agent
 │   ├── docker-compose.yml
 │   ├── package.json
-│   ├── prisma/
-│   ├── app/                 # Next.js App Router
-│   ├── components/
+│   ├── app/                 # Aplikasi utama
 │   └── ...                  # 👤 HUMAN: Code review & testing manual
 │
 ├── tests/                    # [TEST] Output dari Tester Agent
-│   ├── unit/
-│   ├── integration/
 │   └── e2e/                 # 👤 HUMAN: Verify test results
 │
 ├── logs/                     # [TRACKING] Auto-generated logs
 │   ├── development/         # Developer Agent logs
-│   │   ├── dev_001_database_schema.md
-│   │   ├── dev_002_auth_system.md
-│   │   └── ...
 │   ├── testing/             # Tester Agent logs
-│   │   └── test_*.md
 │   └── fixing/              # Bug fixing logs
-│       └── fixing_*.md
 │
 └── documentation/            # [FINAL] Technical Writer output
     └── FSD_{{projectName}}.md       # Functional Specification Document
@@ -129,391 +137,19 @@ root/
 
 ## 🤖 AI Agent Personas & Capabilities
 
-Setiap Agent memiliki **system instruction** yang tersimpan di `.github/prompts/` dan dapat dipanggil via slash command.
-
-**Total: 8 Specialized Agents**
-
-### 1. **Initiator Agent** (`/initiator`)
-**Role:** Project Initiator & Product Manager
-
-**Capabilities:**
-- ✅ Mengubah ide kasar menjadi `project_overview.md` yang terstruktur
-- ✅ Menentukan tech stack berdasarkan kebutuhan
-- ✅ Mendefinisikan UI/UX guidelines (color palette, typography, component library)
-- ✅ Membuat development roadmap & timeline
-
-**Input Example:**
-```
-/initiator
-
-"Aplikasi manajemen booking kapal wisata Labuan Bajo, 
-pakai Next.js, harus ada payment gateway dan backoffice 
-untuk admin."
-```
-
-**Output:**
-- `project_overview.md` (complete dengan target audience, tech stack, roadmap)
-
-**👤 Human Task:**
-- Review `project_overview.md`
-- Approve atau minta revisi (tech stack, UI guidelines, timeline)
-
----
-
-### 2. **PM Agent** (`/pm`) ⭐ NEW
-**Role:** Project Manager & Task Coordinator
-
-**Capabilities:**
-- ✅ Membuat dan mengelola task list di `task/task_list.md`
-- ✅ Memecah specifications menjadi actionable tasks dengan priority (P0-P3)
-- ✅ Tracking status setiap task (not_started → dev → testing → passed)
-- ✅ Mengelola dependencies antar task
-- ✅ Generate project status reports
-- ✅ Monitoring progress dari development logs
-- ✅ Mengidentifikasi blockers dan bottlenecks
-
-**When to Use:**
-- Setelah Analyst membuat specifications (untuk create task list)
-- Saat ingin cek project progress
-- Saat perlu update task status setelah development/testing
-- Saat planning sprint atau prioritization
-
-**Input Example:**
-```
-/pm
-
-"Buat task list berdasarkan semua specifications yang sudah ada"
-```
-
-**Output:**
-- `task/task_list.md` dengan struktur:
-  - Priority sections (P0: Critical → P3: Low)
-  - Task format: TASK-XXX dengan spec reference, status, dependencies
-  - Summary: Total tasks, completed, in progress, blocked
-- `task/PROJECT_STATUS_REPORT.md` (jika diminta generate report)
-
-**Task Status Flow:**
-```
-not_started → dev (Developer working) → ready_to_test (Dev complete)
-           → testing_ready (Test scenarios created) → testing (Tester running)
-           → passed/failed → human_validated
-```
-
-**Priority Levels:**
-- **P0 (Critical):** Blockers, production bugs, foundational features
-- **P1 (High):** Core features, important bugs
-- - **P2 (Medium):** Enhancement, minor features
-- **P3 (Low):** Nice-to-have, future improvements
-
-**👤 Human Task:**
-- Review task priorities (sesuai bisnis priority?)
-- Validate task breakdown (granularity OK?)
-- Approve task assignments
-- Manual validation setelah task passed (human_validated status)
-
-**Workflow Integration:**
-```
-[Analyst] Create specs → [PM] Generate task list
-  ↓
-[Developer] Pick task → Update status: dev → ready_to_test
-  ↓
-[Tester] Create tests → Update status: testing_ready → testing → passed
-  ↓
-[PM] Monitor progress → Generate status reports
-```
-
----
-
-### 3. **Analyst Agent** (`/analyst`)
-**Role:** Lead System Analyst & DevOps Architect
-
-**Capabilities:**
-- ✅ Membaca `project_overview.md` untuk context
-- ✅ Membuat spesifikasi infrastruktur (Docker, database schema)
-- ✅ Membuat spesifikasi fitur (user stories, API contracts, UI mockups)
-- ✅ Memecah fitur besar menjadi atomic specifications (1 file = 1 user story)
-- ✅ Validasi tech stack sudah terisi sebelum lanjut
-
-**Critical Rule:**
-- **WAJIB** membuat `000_spec_environment_setup.md` terlebih dahulu sebelum spec fitur
-
-**Input Example:**
-```
-/analyst
-
-"Buat spesifikasi untuk fitur Booking Management"
-```
-
-**Output:**
-- `specifications/004_spec_booking_management.md`
-- Atau breakdown menjadi multiple atomic specs jika fitur terlalu besar
-
-**👤 Human Task:**
-- Review spesifikasi (apakah sesuai kebutuhan bisnis?)
-- Check API contracts & database schema
-- Approve sebelum Developer mulai coding
-
-**Workflow Integration:**
-```
-[Analyst] Create specification
-  ↓
-[PM] Create task from spec → Add to task/task_list.md
-  ↓
-[Developer] Pick task and implement
-```
-
----
-
-### 4. **Developer Agent** (`/developer`)
-**Role:** Senior Full-Stack Developer
-
-**Capabilities:**
-- ✅ Membaca spesifikasi dari Analyst
-- ✅ Menulis kode (frontend, backend, database migration)
-- ✅ Mengikuti coding standards & best practices
-- ✅ Membuat development log otomatis (`logs/development/dev_*.md`)
-- ✅ Menjalankan build & check errors
-- ✅ Fixing bugs berdasarkan error feedback
-- ✅ **Update task status** di `task/task_list.md` (not_started → dev → ready_to_test)
-
-**Input Example:**
-```
-/developer
-
-"Implementasikan SPEC-004 (Pricing Configuration Module)"
-```
-
-**Output:**
-- Kode di `codes/` (API routes, components, database schema)
-- `logs/development/dev_004_pricing_module.md` (log perubahan)
-
-**👤 Human Task:**
-- Code review (check logic, security, performance)
-- Manual testing di browser/Postman
-- Approve atau minta fixing
-
-**Task Management Workflow:**
-```
-[Developer] Read task/task_list.md → Find task with status "not_started"
-  ↓
-[Developer] Update status: not_started → dev (set "Assigned To: Developer Agent")
-  ↓
-[Developer] Implement feature → Create development log
-  ↓
-[Developer] Update status: dev → ready_to_test (with timestamp)
-```
-
----
-
-### 5. **Tester Agent** (`/tester`)
-**Role:** QA Engineer & Test Automation Specialist
+Dalam workflow ini, kita memecah siklus SDLC (Software Development Life Cycle) menjadi 8 **persona agen terspesialisasi**:
 
-**Capabilities:**
-- ✅ Membuat unit tests, integration tests, E2E tests
-- ✅ Menjalankan tests di terminal
-- ✅ Menganalisis test failures & memberikan fixing recommendation
-- ✅ Membuat testing log (`logs/testing/test_*.md`)
-- ✅ Self-healing: Memperbaiki tests yang broken karena code changes
-- ✅ **Update task status** di `task/task_list.md` (ready_to_test → testing_ready → testing → passed/failed)
+1. **Initiator Agent** (`/initiator`) - Project kickoff & overview
+2. **PM Agent** (`/pm`) - Task management & coordination
+3. **Analyst Agent** (`/analyst`) - Technical specifications
+4. **Developer Agent** (`/developer`) - Code implementation (termasuk Repo Management)
+5. **Tester Agent** (`/tester`) - Test automation & QA (termasuk Repo Management)
+6. **Fixer Agent** (`/fixer`) - Bug fixing & debugging (termasuk Repo Management)
+7. **SysArch Agent** (`/sysarch`) - Infrastructure & deployment planning
+8. **Document Agent** (`/document`) - Final documentation
 
-**Input Example:**
-```
-/tester
-
-"Buat dan jalankan test untuk Pricing Configuration API"
-```
-
-**Output:**
-- Test files di `tests/`
-- Terminal execution results
-- `logs/testing/test_004_pricing.md`
-
-**👤 Human Task:**
-- Verify test coverage (apakah sudah lengkap?)
-- Check test results (all green?)
-- Manual exploratory testing untuk edge cases
-
-**Task Management Workflow:**
-```
-[Tester] Read task/task_list.md → Find task with status "ready_to_test"
-  ↓
-[Tester] Create test scenarios → Update status: ready_to_test → testing_ready
-  ↓
-[Tester] Run tests → Update status: testing_ready → testing
-  ↓
-[Tester] Check results → Update status: testing → passed (or failed)
-```
-
----
-
-### 6. **Fixer Agent** (`/fixer`)
-**Role:** Bug Hunter & Debugging Specialist
-
-**Capabilities:**
-- ✅ Menganalisis error messages (compile errors, runtime errors, test failures)
-- ✅ Membaca stack trace dan pinpoint root cause
-- ✅ Memperbaiki bugs dengan minimal side effects
-- ✅ Membuat fixing log (`logs/fixing/fixing_*.md`)
-- ✅ Validasi fix dengan menjalankan tests
-- ✅ Regression testing (pastikan fix tidak break fitur lain)
-- ✅ **Update task status** di `task/task_list.md` (failed → fixing → ready_to_test)
-
-**When to Use:**
-- Setelah Developer bikin code tapi ada errors
-- Setelah Tester report bugs
-- Production bugs yang perlu hotfix
-- Build failures di CI/CD
-
-**Input Example:**
-```
-/fixer
-
-"Ada bug di create booking: DP amount tidak ter-kalkulasi.
-Error: Cannot read property 'totalPrice' of undefined
-File: app/api/backoffice/bookings/route.ts:45
-
-Error terjadi saat user submit booking form dengan pax > 10"
-```
-
-**Output:**
-- Fixed code di `codes/`
-- `logs/fixing/fixing_003_booking_dp_calculation.md` (detailed analysis + solution)
-- Test execution result (verify fix works)
-
-**👤 Human Task:**
-- Verify fix logic (apakah benar-benar solve root cause?)
-- Check for side effects (fitur lain masih jalan?)
-- Manual testing dengan scenario yang sama
-- Approve atau minta alternative solution
-
-**Workflow Integration:**
-```
-Developer creates code → Error found
-  ↓
-Fixer analyzes → Fix bug → Run tests
-  ↓
-All green? → Done ✅
-Not green? → Iterate fix
-```
-
-**Task Management Workflow:**
-```
-[Tester] Find bugs → Update task status: passed → failed
-  ↓
-[Fixer] Read task/task_list.md → Find task with status "failed"
-  ↓
-[Fixer] Update status: failed → fixing (set "Assigned To: Fixer Agent")
-  ↓
-[Fixer] Fix bugs → Create fixing log
-  ↓
-[Fixer] Update status: fixing → ready_to_test (back to Tester)
-```
-
----
-
-### 7. **SysArch Agent** (`/sysarch`)
-**Role:** System Architecture & Operations Specialist
-
-**Capabilities:**
-- ✅ Menganalisis application requirements dari codebase dan specifications
-- ✅ Mendesain server specifications (CPU, RAM, Storage, Bandwidth)
-- ✅ Merencanakan infrastructure architecture (dev, staging, production)
-- ✅ Mengestimasi resource requirements & costs
-- ✅ Merekomendasikan deployment strategies (VPS, cloud, containerized)
-- ✅ Membuat operational guidelines (monitoring, backup, scaling, disaster recovery)
-- ✅ Mengoptimasi biaya infrastruktur
-
-**When to Use:**
-- Sebelum deployment ke production (infrastructure planning)
-- Saat aplikasi mulai lambat (performance analysis & scaling recommendation)
-- Saat budget review (cost optimization analysis)
-- Saat planning capacity untuk high season
-
-**Input Example:**
-```
-/sysarch
-
-"Analyze current codebase and design server specifications 
-for production deployment. Target: 100 concurrent users, 
-50 bookings/day, 99.9% uptime."
-```
-
-**Output:**
-- `architecture/current_state.md` - Application analysis
-- `architecture/server_specifications.md` - Detailed server specs
-- `architecture/deployment_plan.md` - Step-by-step deployment guide
-- `architecture/cost_analysis.md` - Infrastructure cost breakdown
-- `architecture/monitoring_plan.md` - Observability & alerting setup
-
-**👤 Human Task:**
-- Jawab questions tentang load requirements (concurrent users, transactions, etc.)
-- Review server specifications (sesuai budget?)
-- Approve deployment plan
-- Check cost estimates (sustainable?)
-- Decide cloud provider preference
-
-**Critical Questions SysArch Will Ask:**
-1. **User Load:** Concurrent users, growth rate, peak season multiplier
-2. **Transaction Volume:** Bookings/day, payments/day, API requests/min
-3. **Data & Storage:** File uploads, data retention, backup requirements
-4. **Performance:** API response time, page load time, CDN needs
-5. **Availability:** Uptime target (99%, 99.9%, 99.99%), HA requirements
-6. **Budget:** Monthly infrastructure budget, cloud provider preference
-7. **Security:** SSL, WAF, DDoS protection, compliance (PCI-DSS, GDPR, UU PDP)
-
-**Example Workflow:**
-```
-[SysArch] Ask requirements → [👤 Human] Answer questions
-  ↓
-[SysArch] Analyze codebase → Design architecture
-  ↓
-[SysArch] Create specs & deployment plan → [👤 Human] Review & Approve
-  ↓
-[Developer/SysArch] Deploy to production
-  ↓
-[SysArch] Setup monitoring → [👤 Human] Monitor metrics
-```
-
----
-
-### 8. **Document Agent** (`/document`)
-**Role:** Technical Writer
-
-**Capabilities:**
-- ✅ Menggabungkan semua specifications menjadi FSD (Functional Specification Document)
-- ✅ Generate API documentation
-- ✅ Membuat user manual / deployment guide
-- ✅ Format markdown yang professional & readable
-
-**Input Example:**
-```
-/document
-
-"Generate FSD lengkap dari semua specifications"
-```
-
-**Output:**
-- `documentation/FSD_{{projectName}}.md`
-- `documentation/API_Documentation.md`
-
-**👤 Human Task:**
-- Final review dokumentasi
-- Share ke stakeholder (investor, klien)
-
----
-
-## 🤖 Peran & Perintah (Slash Commands)
-
-| Agent | Command | Primary Function | Output | Human Review |
-| --- | --- | --- | --- | --- |
-| **Initiator** | `/initiator` | Project kickoff & overview | `project_overview.md` | ⚠️ **CRITICAL** |
-| **PM** | `/pm` | Task management & coordination | `task/task_list.md`, `task/PROJECT_STATUS_REPORT.md` | ✅ **MEDIUM** |
-| **Analyst** | `/analyst` | Technical specifications | `specifications/*.md` | ⚠️ **HIGH** |
-| **Developer** | `/developer` | Code implementation | `codes/*`, `logs/development/` | ⚠️ **HIGH** |
-| **Tester** | `/tester` | Test automation & QA | `tests/*`, `logs/testing/` | ✅ **MEDIUM** |
-| **Fixer** | `/fixer` | Bug fixing & debugging | `codes/*`, `logs/fixing/` | ⚠️ **HIGH** |
-| **SysArch** | `/sysarch` | Infrastructure & deployment planning | `architecture/*` | ⚠️ **CRITICAL** |
-| **Document** | `/document` | Final documentation | `documentation/*.md` | ✅ **LOW** |
+> 🔗 **Detail lengkap** mengenai cara kerja, rules, integrasi alur tugas, serta kemampuan (*capabilities*) dari tiap-tiap agen dapat dibaca di panduan terpisah:
+> 👉 **[BACA: Panduan Persona & Kemampuan Agen (AGENT_PERSONAS.md)](./AGENT_PERSONAS.md)**
 
 ---
 
@@ -1254,13 +890,7 @@ tambahkan test untuk edge cases:
 - Booking dengan tanggal di masa lalu"
 ```
 
----
-
 ### **7. Bugs di Production** 🐛
-
----
-
-### **5. Bugs di Production** 🐛
 **Symptom:** User report bug di production, perlu hotfix cepat
 
 **Fix:**
@@ -1839,6 +1469,3 @@ Include:
 - SysArch Agent = **Infrastructure Guardian** (keeps costs low, performance high) ⭐ NEW
 
 **Together = Unstoppable** 💪🤖👤
-- Human = **Navigator** (makes sure direction is correct)
-
-**Together = Unstoppable** 💪🤖👤

package/template/agent/workflows/_shared/git-branch-management.md

@@ -0,0 +1,25 @@
+# Git Branch Management (Shared)
+
+## Rules
+1. **NEVER** commit/push langsung ke `main` atau `development`.
+2. **PENTING — Struktur Repo:** Workspace ini terdiri dari DUA repo git terpisah:
+   - **Agent repo** (root): `{project-name}/` — berisi semua file agent, spec, task, logs. Jangan commit kode produk di sini.
+   - **Product repo** (subfolder): `codes/` — repo git terpisah yang di-push ke `{repo-url}`. Semua operasi git untuk kode produk dilakukan DI DALAM folder `codes/`.
+3. **Semua perintah git untuk kode produk harus dijalankan dari dalam folder `codes/`.**
+4. **Konvensi Nama Branch:** gunakan format `feature/nama-fitur`, `fix/nama-bug`, atau `test/nama-fitur`.
+5. **Konvensi Commit (CRITICAL):** Wajib menggunakan **Conventional Commits** format:
+   - `feat: [pesan]` untuk fitur baru.
+   - `fix: [pesan]` untuk bug fix.
+   - `chore: [pesan]` untuk update tooling/config.
+   - `docs: [pesan]` untuk perubahan dokumentasi.
+   - `test: [pesan]` untuk penambahan test.
+
+## Steps
+1. **Cek branch saat ini** dengan `git -C codes/ branch --show-current`.
+2. **Cek apakah ada perubahan yang belum di-commit** dengan `git -C codes/ status`.
+   - **Jika ada perubahan belum ter-commit:** HENTIKAN pekerjaan. Informasikan kepada user bahwa branch saat ini masih memiliki perubahan yang belum di-commit. Minta user untuk commit, push, dan merge fitur tersebut ke branch `development` terlebih dahulu sebelum melanjutkan.
+3. **Jika working tree clean:**
+   - Pindah ke branch `development`: `git -C codes/ checkout development`.
+   - Pull perubahan terbaru: `git -C codes/ pull origin development`.
+   - Buat atau pindah ke branch yang sesuai dengan task: `git -C codes/ checkout -b [type]/[nama-task]`.
+4. **JANGAN lakukan commit dan push otomatis** setelah pekerjaan selesai. Hasil pekerjaan perlu diverifikasi oleh user terlebih dahulu.

package/template/agent/workflows/_shared/state-management.md

@@ -0,0 +1,5 @@
+# State Management (Shared)
+
+- Baca `state/context.json` di awal session untuk memahami konteks project saat ini.
+- Update `state/context.json` di akhir session jika ada perubahan state atau status penting.
+- Jika ada operan data spesifik atau context handoff ke agent lain, tulis ke `state/agent_handoff.json`.

package/template/agent/workflows/analyst.md

@@ -7,9 +7,9 @@
 2. **Validate:**
     - Apakah "Tech Stack" dan "UI Guidelines" di `project_overview.md` sudah terisi?
     - Jika KOSONG/BELUM JELAS: **BERHENTI**. Ajukan pertanyaan klarifikasi kepada saya untuk melengkapinya dulu. Jangan lanjut sebelum ini jelas.
-3.  **Directory Check:** Cek/Buat folder `specification/`.
+3.  **Directory Check:** Cek/Buat folder `specifications/`.
 4.  **INFRASTRUCTURE CHECK (CRITICAL):**
-    - Cek apakah file `specification/000_spec_environment_setup.md` sudah ada?
+    - Cek apakah file `specifications/000_spec_environment_setup.md` sudah ada?
     - **JIKA BELUM ADA:**
         - Abaikan permintaan fitur user saat ini.
         - Prioritas utama adalah membuat spesifikasi Environment.
@@ -52,7 +52,9 @@
 
 9.  **Review & Finalize:**
     - Pastikan spesifikasi lengkap, jelas, dan sesuai standar dokumentasi.
-    - Simpan file di `specification/` dengan format penamaan yang benar.
+    - Simpan file di `specifications/` dengan format penamaan yang benar.
 
 **INPUT SAYA:**
-"[INPUT USER DISINI]"
+"[INPUT USER DISINI]"
+## State Management
+> 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`

package/template/agent/workflows/developer.md

@@ -3,17 +3,20 @@
 
 **INSTRUCTION STEPS:**
 1.  **Load Context:**
-    - Baca file spesifikasi target (misal: `specifications/001_...md`).
     - **BACA file `task/task_list.md`** untuk menemukan task yang akan dikerjakan.
-    - Temukan file detail task di `task/[TASK-ID]_[nama-task].md` yang sesuai.
+    - Temukan file detail task di `task/[TASK-ID]_[nama-task]/task_detail.md` yang sesuai.
+    - Baca file spesifikasi target (misal: `specifications/001_...md`).
 
 2.  **Update Task Status - START (CRITICAL):**
     - Di `task/task_list.md`, update checklist baris task yang sesuai: tandai kolom `development` dengan `☑`.
-    - Di file detail task `task/[TASK-ID]_[nama-task].md`, **APPEND** entry baru ke Status Log:
+    - Di file detail task `task/[TASK-ID]_[nama-task]/task_detail.md`, **APPEND** entry baru ke Status Log:
       ```
       | [YYYY-MM-DD HH:MM] | dev agent | development started | - |
       ```
 
+2b.  **Repo Management (CRITICAL - lakukan sebelum mulai coding):**
+    > 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/git-branch-management.md` untuk aturan git branch dan folder struktur.
+
 3.  **Directory Check:** Cek apakah folder `codes/` ada. Jika tidak, **BUAT FOLDERNYA**.
 
 4.  **Action (Coding):**
@@ -23,6 +26,7 @@
     - Simpan file source code di dalam folder `codes/`.
     - Perhatikan detail UI/UX jika ada instruksi visual. **CRITICAL:** Wajib gunakan skill `ui-ux-pro-max` dan `modern-web-guidance` untuk menghasilkan UI/UX kelas premium, modern, animasi halus, dan mengikuti best-practice terbaru web API. Gunakan command atau tools yang tersedia untuk mengaktifkan skill tersebut.
     - Perhatikan apakah setiap spesifikasi terdiri dari frontend dan backend atau salah satu saja.
+    - **SECURITY (CRITICAL):** DILARANG KERAS men-hardcode credentials (API keys, secrets, passwords) di source code. Semua harus via environment variables (`.env`). Pastikan key baru didaftarkan di `.env.example`.
     - Lakukan *Self-Reflection*: "Apakah kode ini aman? Apakah efisien?"
     - Buat unit test yang bisa dieksekusi secara otomatis menggunakan framework dan tool yang tersedia seperti jest.
 
@@ -57,10 +61,12 @@
 
 6.  **Update Task Status - COMPLETE (CRITICAL):**
     - Di `task/task_list.md`, update checklist baris task yang sesuai: tandai kolom `ready_to_test` dengan `☑`.
-    - Di file detail task `task/[TASK-ID]_[nama-task].md`, **APPEND** entry baru ke Status Log:
+    - Di file detail task `task/[TASK-ID]_[nama-task]/task_detail.md`, **APPEND** entry baru ke Status Log:
       ```
       | [YYYY-MM-DD HH:MM] | dev agent | ready to test | [catatan penting jika ada] |
       ```
 
 **INPUT SAYA:**
-"Tolong implementasikan spesifikasi berikut: [NAMA FILE SPEC]"
+"Tolong implementasikan spesifikasi berikut: [NAMA FILE SPEC]"
+## State Management
+> 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`