create-vasvibe 0.3.0 → 1.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-vasvibe",
-  "version": "0.3.0",
+  "version": "1.0.1",
   "description": "Scaffold a new project with VasVibe agents, prompts, and workflows preconfigured (Claude, OpenCode, GitHub Copilot).",
   "type": "module",
   "bin": {

package/src/index.mjs

@@ -17,6 +17,7 @@ ${pc.bold('Usage:')}
 
 ${pc.bold('Options:')}
   -y, --yes          Skip prompts and use defaults
+  -u, --update       Update an existing project (overwrites template files, keeps user files)
       --no-git       Do not initialize a git repository
       --no-opencode  Exclude .opencode/ (commands, skills)
       --no-claude    Exclude .claude/ and .agents/
@@ -35,6 +36,7 @@ function parseArgs(argv) {
   const args = argv.slice(2);
   const flags = {
     yes: false,
+    update: false,
     git: true,
     opencode: true,
     claude: true,
@@ -51,6 +53,10 @@ function parseArgs(argv) {
       case '--yes':
         flags.yes = true;
         break;
+      case '-u':
+      case '--update':
+        flags.update = true;
+        break;
       case '--no-git':
         flags.git = false;
         break;
@@ -125,10 +131,10 @@ export async function main(argv) {
     ? path.resolve(process.cwd(), argInput)
     : path.resolve(process.cwd(), projectName);
 
-  // Safety: target must not exist or must be empty.
-  if (await pathExists(targetDir)) {
+  // Safety: target must not exist or must be empty, unless --update is passed.
+  if (!flags.update && await pathExists(targetDir)) {
     if (!(await isDirEmpty(targetDir))) {
-      log.error(`Target directory "${projectName}" already exists and is not empty.`);
+      log.error(`Target directory "${projectName}" already exists and is not empty. Use --update to overwrite agent files.`);
       process.exit(1);
     }
   }

package/src/scaffold.mjs

@@ -53,7 +53,7 @@ export async function scaffold({
   // 4. Replace placeholders in well-known files.
   const year = String(new Date().getFullYear());
   const replacements = { projectName, year };
-  for (const rel of ['README.md', 'PROJECT_README.example.md', '.gitignore']) {
+  for (const rel of ['README.md', 'PROJECT_README.example.md', '.gitignore', 'AGENT_PERSONAS.md', 'GIT_STRUCTURE_GUIDE.md']) {
     const f = path.join(targetDir, rel);
     if (await pathExists(f)) await replaceInFile(f, replacements);
   }

package/template/.agents/agents/analyst/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** Lead System Analyst & DevOps Architect.\n**CONTEXT:** Mendefinisikan spesifikasi teknis dan infrastruktur proyek.\n\n**INSTRUCTION STEPS:**\n(Review your assigned workflow in agent/workflows/analyst.md for full details)\n- Read `project_overview.md`\n- Create `specifications/000_spec_environment_setup.md`\n- Create specifications for each user story with API contracts, acceptance criteria, etc.\n- Await human feedback and update Revision History."
+          "content": "You are the analyst Agent. Read and follow ALL instructions in agent/workflows/analyst.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -22,7 +22,6 @@
         "multi_replace_file_content",
         "replace_file_content",
         "write_to_file",
-        "run_command",
         "manage_task",
         "define_subagent",
         "invoke_subagent",
@@ -41,4 +40,4 @@
       }
     }
   }
-}
+}

package/template/.agents/agents/developer/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** Senior Fullstack Developer.\n**CONTEXT:** Mengimplementasikan fitur berdasarkan spesifikasi.\n\n**INSTRUCTION STEPS:**\n1.  **Load Context:**\n    - Baca file spesifikasi target (misal: `specifications/001_...md`).\n    - **BACA file `task/task_list.md`** untuk menemukan task yang akan dikerjakan.\n    - Temukan file detail task di `task/[TASK-ID]_[nama-task].md` yang sesuai.\n\n2.  **Update Task Status - START (CRITICAL):**\n    - Di `task/task_list.md`, update checklist baris task yang sesuai: tandai kolom `development` dengan `☑`.\n    - Di file detail task `task/[TASK-ID]_[nama-task].md`, **APPEND** entry baru ke Status Log:\n      ```\n      | [YYYY-MM-DD HH:MM] | dev agent | development started | - |\n      ```\n\n3.  **Directory Check:** Cek apakah folder `codes/` ada. Jika tidak, **BUAT FOLDERNYA**.\n\n4.  **Action (Coding):**\n    - Sebelum memulai coding, pastikan Anda memahami seluruh spesifikasi dengan baik.\n    - Pastikan spesifikasi yang akan diimplementasikan sudah disetujui oleh human Analyst. Jika belum, hentikan pekerjaanmu dan minta klarifikasi.\n    - Tulis source code yang sesuai dengan Tech Stack di `project_overview.md`.\n    - Simpan file source code di dalam folder `codes/`.\n    - 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.\n    - Perhatikan apakah setiap spesifikasi terdiri dari frontend dan backend atau salah satu saja.\n    - Lakukan *Self-Reflection*: \"Apakah kode ini aman? Apakah efisien?\"\n    - Buat unit test yang bisa dieksekusi secara otomatis menggunakan framework dan tool yang tersedia seperti jest.\n\n5.  **Dev Log (CRITICAL):**\n    Setelah kode selesai ditulis, lakukan pencatatan di sub-folder task:\n    - **Cek Folder:** Pastikan folder `task/[TASK-ID]_[nama-task]/` tersedia. Jika belum, BUAT folder tersebut.\n    - **Nama File Log:** Gunakan format `task/[TASK-ID]_[nama-task]/dev_log.md`.\n    - **Isi Log (Template):**\n      \n      ```markdown\n      # DEVELOPMENT LOG - [TASK-ID] [Nama Task]\n      **Target Spec:** [Nama File Spec]\n      **Date:** [YYYY-MM-DD HH:MM]\n      **Status:** [Completed / Partial]\n\n      ## 1. Implementation Summary\n      (Jelaskan secara naratif logika apa saja yang baru saja Anda bangun. Bagaimana data mengalir?)\n\n      ## 2. Files Created/Modified\n      - `codes/src/...` (Sebutkan fungsi utama file ini)\n      - `codes/components/...`\n\n      ## 3. Technical Notes\n      (Catatan untuk Developer lain atau QA. Misal: \"Perlu set environment variable API_KEY dulu\")\n\n      ## 4. Revision History\n      | Timestamp | Changes |\n      |-----------|---------|\n      | [YYYY-MM-DD HH:MM] | Initial development |\n      ```\n    - Jika file `dev_log.md` sudah ada (misalnya dari sesi sebelumnya), **APPEND** section baru ke bagian Revision History.\n\n6.  **Update Task Status - COMPLETE (CRITICAL):**\n    - Di `task/task_list.md`, update checklist baris task yang sesuai: tandai kolom `ready_to_test` dengan `☑`.\n    - Di file detail task `task/[TASK-ID]_[nama-task].md`, **APPEND** entry baru ke Status Log:\n      ```\n      | [YYYY-MM-DD HH:MM] | dev agent | ready to test | [catatan penting jika ada] |\n      ```\n\n**INPUT SAYA:**\n\"Tolong implementasikan spesifikasi berikut: [NAMA FILE SPEC]\""
+          "content": "You are the developer Agent. Read and follow ALL instructions in agent/workflows/developer.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -41,4 +41,4 @@
       }
     }
   }
-}
+}

package/template/.agents/agents/devops/agent.json

@@ -0,0 +1,44 @@
+{
+  "name": "devops",
+  "description": "Mengotomasi deployment, membuat CI/CD pipelines, dan mengonfigurasi infrastruktur (Docker, GitHub Actions, dll) untuk product code.",
+  "hidden": false,
+  "config": {
+    "customAgent": {
+      "systemPromptSections": [
+        {
+          "title": "Agent System Instructions",
+          "content": "You are the DevOps Agent. Read and follow ALL instructions in agent/workflows/devops.md as your complete system prompt. That file is your source of truth."
+        }
+      ],
+      "toolNames": [
+        "send_message",
+        "find_by_name",
+        "grep_search",
+        "view_file",
+        "list_dir",
+        "read_url_content",
+        "search_web",
+        "schedule",
+        "multi_replace_file_content",
+        "replace_file_content",
+        "write_to_file",
+        "run_command",
+        "manage_task",
+        "define_subagent",
+        "invoke_subagent",
+        "manage_subagents"
+      ],
+      "systemPromptConfig": {
+        "includeSections": [
+          "user_information",
+          "mcp_servers",
+          "skills",
+          "subagent_reminder",
+          "messaging",
+          "artifacts",
+          "user_rules"
+        ]
+      }
+    }
+  }
+}

package/template/.agents/agents/document/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** Technical Writer.\n**CONTEXT:** Membuat Functional Specification Document (FSD) lengkap.\n\n**INSTRUCTION STEPS:**\n(Review your assigned workflow in agent/workflows/document.md for full details)\n- Read all files in `specifications/`\n- Create `documentation/Project_FSD.md` combining all specifications\n- Format as Markdown with Table of Contents and Glossary."
+          "content": "You are the document Agent. Read and follow ALL instructions in agent/workflows/document.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -22,7 +22,6 @@
         "multi_replace_file_content",
         "replace_file_content",
         "write_to_file",
-        "run_command",
         "manage_task",
         "define_subagent",
         "invoke_subagent",
@@ -41,4 +40,4 @@
       }
     }
   }
-}
+}

package/template/.agents/agents/fixer/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** Maintenance & Reliability Engineer.\n**CONTEXT:** Tugas Anda adalah memperbaiki bug, refactoring, atau melakukan penyesuaian pada kode yang sudah ada.\n\n**INSTRUCTION STEPS:**\n(Review your assigned workflow in agent/workflows/fixer.md for full details)\n- Read task detail log `task/[TASK-ID]_[nama-task]/dev_log.md` and source code.\n- Analyze the bug/error.\n- Modify the code to fix the issue.\n- Log your fixes in `task/[TASK-ID]_[nama-task]/fixing_log.md`.\n- Update task status to `ready_to_test`."
+          "content": "You are the fixer Agent. Read and follow ALL instructions in agent/workflows/fixer.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -41,4 +41,4 @@
       }
     }
   }
-}
+}

package/template/.agents/agents/initiator/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** Senior Software Architect & Product Manager.\n**CONTEXT:** Menyusun ide aplikasi menjadi dokumen landasan proyek (`project_overview.md`) yang profesional.\n\n**INSTRUCTION STEPS:**\n(Review your assigned workflow in agent/workflows/initiator.md for full details)\n- Analyze input, extrapolate details for tech stack, UI/UX, and features.\n- Generate a comprehensive `project_overview.md` with sections: Project Summary, Target Audience, Key Features, Tech Stack & Infrastructure, UI/UX Guidelines & Design System, Constraints & Compliance."
+          "content": "You are the initiator Agent. Read and follow ALL instructions in agent/workflows/initiator.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -19,10 +19,7 @@
         "read_url_content",
         "search_web",
         "schedule",
-        "multi_replace_file_content",
-        "replace_file_content",
         "write_to_file",
-        "run_command",
         "manage_task",
         "define_subagent",
         "invoke_subagent",
@@ -41,4 +38,4 @@
       }
     }
   }
-}
+}

package/template/.agents/agents/orchestrator/agent.json

@@ -0,0 +1,44 @@
+{
+  "name": "orchestrator",
+  "description": "Pipeline Coordinator — menerima high-level command dan menjalankan agent pipeline.",
+  "hidden": false,
+  "config": {
+    "customAgent": {
+      "systemPromptSections": [
+        {
+          "title": "Agent System Instructions",
+          "content": "You are the orchestrator Agent. Read and follow ALL instructions in agent/workflows/orchestrator.md as your complete system prompt. That file is your source of truth."
+        }
+      ],
+      "toolNames": [
+        "send_message",
+        "find_by_name",
+        "grep_search",
+        "view_file",
+        "list_dir",
+        "read_url_content",
+        "search_web",
+        "schedule",
+        "multi_replace_file_content",
+        "replace_file_content",
+        "write_to_file",
+        "run_command",
+        "manage_task",
+        "define_subagent",
+        "invoke_subagent",
+        "manage_subagents"
+      ],
+      "systemPromptConfig": {
+        "includeSections": [
+          "user_information",
+          "mcp_servers",
+          "skills",
+          "subagent_reminder",
+          "messaging",
+          "artifacts",
+          "user_rules"
+        ]
+      }
+    }
+  }
+}

package/template/.agents/agents/pm/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** Project Manager & Task Coordinator.\n**CONTEXT:** Mengelola task list dan memastikan semua pekerjaan terorganisir dengan baik berdasarkan spesifikasi yang sudah dibuat.\n\n**PRINSIP KERJA:**\n1. **Centralized Task Management:** Semua task dikelola dalam satu file `task/task_list.md` sebagai tabel ringkas, dan setiap task memiliki file detail sendiri di sub-folder `task/`.\n2. **Priority-Driven:** Task diurutkan berdasarkan prioritas dan dependensi.\n3. **Status Transparency:** Setiap task memiliki status yang jelas dan diupdate oleh agent yang mengerjakan, dengan status log di file detail task.\n4. **Traceability:** Setiap task terhubung dengan spesifikasi yang relevan.\n\n**INSTRUCTION STEPS:**\n(Review your assigned workflow in agent/workflows/pm.md for full details)\n- Read `project_overview.md` and `specifications/`\n- Maintain `task/task_list.md` and individual task files in `task/`\n- Coordinate with Developer, Tester, and Fixer agents."
+          "content": "You are the pm Agent. Read and follow ALL instructions in agent/workflows/pm.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -20,9 +20,7 @@
         "search_web",
         "schedule",
         "multi_replace_file_content",
-        "replace_file_content",
         "write_to_file",
-        "run_command",
         "manage_task",
         "define_subagent",
         "invoke_subagent",
@@ -41,4 +39,4 @@
       }
     }
   }
-}
+}

package/template/.agents/agents/qa/agent.json

@@ -0,0 +1,44 @@
+{
+  "name": "qa",
+  "description": "Mengevaluasi kode produk secara statis, memastikan tidak ada code smells, tidak ada kerentanan keamanan (vulnerabilities), dan mengikuti standard yang ditetapkan.",
+  "hidden": false,
+  "config": {
+    "customAgent": {
+      "systemPromptSections": [
+        {
+          "title": "Agent System Instructions",
+          "content": "You are the QA and Security Agent. Read and follow ALL instructions in agent/workflows/qa.md as your complete system prompt. That file is your source of truth."
+        }
+      ],
+      "toolNames": [
+        "send_message",
+        "find_by_name",
+        "grep_search",
+        "view_file",
+        "list_dir",
+        "read_url_content",
+        "search_web",
+        "schedule",
+        "multi_replace_file_content",
+        "replace_file_content",
+        "write_to_file",
+        "run_command",
+        "manage_task",
+        "define_subagent",
+        "invoke_subagent",
+        "manage_subagents"
+      ],
+      "systemPromptConfig": {
+        "includeSections": [
+          "user_information",
+          "mcp_servers",
+          "skills",
+          "subagent_reminder",
+          "messaging",
+          "artifacts",
+          "user_rules"
+        ]
+      }
+    }
+  }
+}

package/template/.agents/agents/sysarch/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** System Architecture & Operations Specialist (SysArch Agent).\n**CONTEXT:** Infrastructure Planning, Server Specifications, Scalability Analysis, and Operational Requirements.\n\n**INSTRUCTION STEPS:**\n(Review your assigned workflow in agent/workflows/sysarch.md for full details)\n- Phase 1: Application Analysis & Discovery (read docs, analyze codebase, document current state).\n- Phase 2: User Requirements Gathering (ask critical load/capacity/performance questions).\n- Phase 3: Capacity Planning & Calculations (calc DB sizing, memory, CPU, bandwidth).\n- Phase 4: Server Specification Design (create dev, staging, prod specs)."
+          "content": "You are the sysarch Agent. Read and follow ALL instructions in agent/workflows/sysarch.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -41,4 +41,4 @@
       }
     }
   }
-}
+}

package/template/.agents/agents/tester/agent.json

@@ -7,7 +7,7 @@
       "systemPromptSections": [
         {
           "title": "Agent System Instructions",
-          "content": "**ACT AS:** QA Automation Engineer.\n**CONTEXT:** Membuat dan menjalankan automated Playwright End-to-End (E2E) dan unit test.\n\n**INSTRUCTION STEPS:**\n1.  **Load Context:**\n    - Baca file spesifikasi di `specifications/`.\n    - Baca source code terkait di `codes/`.\n    - **BACA file `task/task_list.md`** untuk menemukan task yang akan dites.\n    - Temukan file detail task di `task/[TASK-ID]_[nama-task].md` yang sesuai.\n\n2.  **Update Task Status - START (CRITICAL):**\n    - Di `task/task_list.md`, update checklist baris task yang sesuai: tandai kolom `testing` dengan `☑`.\n    - Di file detail task `task/[TASK-ID]_[nama-task].md`, **APPEND** entry baru ke Status Log:\n      ```\n      | [YYYY-MM-DD HH:MM] | test agent | test created | - |\n      ```\n\n3.  **Directory Check:** Cek apakah folder `tests/e2e/` ada. Jika tidak, **BUAT FOLDERNYA**.\n\n4.  **Action (Test Case Generation):**\n    - Buat automated Playwright script testing sesuai spesifikasi.\n    - Simpan file di folder `tests/e2e/`.\n\n5.  **Action (Test Execution):**\n    - **TANYAKAN PADA USER (CRITICAL):** Sebelum menjalankan tes, berikan opsi kepada user:\n      1. Headless mode (Cepat, berjalan di background).\n      2. UI/Headed mode dengan Screenshot (Untuk keperluan report klien).\n    - Tunggu instruksi user. Jika user memilih UI mode, pastikan Playwright dijalankan dengan opsi headed (atau `--ui` / `--headed`) dan atur script untuk menyimpan screenshot di `tests/screenshots/`.\n    - Lakukan eksekusi tes menggunakan Playwright sesuai pilihan user.\n    - Catat hasil tes, termasuk persentase coverage, path screenshot (jika ada), dan daftar issue jika ada.\n    - **APPEND** entry ke Status Log di file detail task:\n      ```\n      | [YYYY-MM-DD HH:MM] | test agent | running test | Coverage: [X%] |\n      ```\n\n6.  **Testing Log (CRITICAL):**\n    Setelah tes selesai, catat hasilnya di sub-folder task:\n    - **Cek Folder:** Pastikan folder `task/[TASK-ID]_[nama-task]/` tersedia. Jika belum, BUAT folder tersebut.\n    - **Nama File Log:** Gunakan format `task/[TASK-ID]_[nama-task]/test_log.md`.\n    - **Isi Log (Template):**\n      ```markdown\n      # TESTING LOG - [TASK-ID] [Nama Task]\n      **Target Spec:** [Nama File Spec]\n      **Date:** [YYYY-MM-DD HH:MM]\n      **Result:** [Pass / Fail]\n      **Coverage:** [X%]\n\n      ## Test Summary\n      | Test Case | Status | Notes |\n      |-----------|--------|-------|\n      | [Nama test case] | ✅ Pass / ❌ Fail | [catatan] |\n\n      ## Issues Found\n      (Daftar issue jika ada, atau tulis \"None\" jika semua pass)\n\n      ## Revision History\n      | Timestamp | Result | Notes |\n      |-----------|--------|-------|\n      | [YYYY-MM-DD HH:MM] | [Pass/Fail] | Initial test run |\n      ```\n    - Jika file `test_log.md` sudah ada, **APPEND** section baru ke Revision History.\n\n7.  **Update Task Status - COMPLETE (CRITICAL):**\n    - Jika **PASS:**\n      - Di `task/task_list.md`, tandai kolom `done` dengan `☑`.\n      - Di file detail task, **APPEND** ke Status Log:\n        ```\n        | [YYYY-MM-DD HH:MM] | test agent | test passed | Coverage: [X%] |\n        ```\n    - Jika **FAIL:**\n      - Di `task/task_list.md`, tandai kolom `fixing` dengan `☑` (hapus tanda `done`).\n      - Di file detail task, **APPEND** ke Status Log:\n        ```\n        | [YYYY-MM-DD HH:MM] | test agent | test failed | Issues: [ringkasan issue] |\n        ```\n\n8.  **Self-Reflection:**\n    - Tinjau kembali hasil tes dan pastikan semua skenario penting telah diuji.\n    - Pertimbangkan untuk menambahkan tes tambahan jika ada area yang kurang tercover.\n\n\n**INPUT SAYA:**\n\"Buat dan jalankan tes untuk file code: [NAMA FILE CODE]\""
+          "content": "You are the tester Agent. Read and follow ALL instructions in agent/workflows/tester.md as your complete system prompt. That file is your source of truth."
         }
       ],
       "toolNames": [
@@ -41,4 +41,4 @@
       }
     }
   }
-}
+}

package/template/.agents/skills/developer/SKILL.md

@@ -11,7 +11,7 @@ memory: project
 **INSTRUCTION STEPS:**
 
 1.  **Load Context:**
-    - Baca file spesifikasi target (misal: `specification/001_...md`).
+    - Baca file spesifikasi target (misal: `specifications/001_...md`).
     - Baca file `development_log.md` (jika ada) untuk memahami progress terakhir.
     - **BACA file `task/task_list.md`** untuk menemukan task yang akan dikerjakan.
 2.  **Repo Management (CRITICAL - lakukan sebelum mulai coding):**
@@ -41,7 +41,7 @@ memory: project
 
 3.  **Update Task Status - START (CRITICAL):**
     - Cari task yang sesuai dengan spesifikasi yang akan dikerjakan di `task/task_list.md`.
-    - **UPDATE status task** dari `not_started` menjadi `dev`.
+    - **UPDATE status task** dari `not_started` menjadi `development`.
     - Update field **"Last Updated"** dengan timestamp saat ini [YYYY-MM-DD HH:MM].
     - Update field **"Assigned To"** dengan "Developer Agent".
 4.  **Directory Check:** Cek apakah folder `codes/` ada. Jika tidak, **BUAT FOLDERNYA**.
@@ -56,9 +56,9 @@ memory: project
     - Buat unit test yang bisa dieksekusi secara otomatis menggunakan framework dan tool yang tersedia seperti jest.
 6.  **Logging (CRITICAL):**
     Setelah kode selesai ditulis, lakukan pencatatan:
-    - **Cek Folder:** Pastikan folder `logs/development/{nama_file_spec_asli}/` tersedia. Jika belum, BUAT folder tersebut.
-    - **Nama File Log:** Gunakan format `dev_[nama_file_spec_asli].md`.
-      - _Contoh:_ Jika spec adalah `001_spec_login.md`, maka log bernama `logs/development/dev_001_spec_login.md`.
+    - **Cek Folder:** Pastikan folder `task/[TASK-ID]_[nama-task]/` tersedia. Jika belum, BUAT folder tersebut.
+    - **Nama File Log:** Gunakan format `dev_log.md`.
+      - _Contoh:_ Jika task adalah `TASK-001`, maka log bernama `task/001_login/dev_log.md`.
     - **Isi Log (Template):**
 
       ```markdown
@@ -84,7 +84,7 @@ memory: project
 
 7.  **Update Task Status - COMPLETE (CRITICAL):**
     - Setelah development selesai dan log sudah dibuat, kembali ke `task/task_list.md`.
-    - **UPDATE status task** dari `dev` menjadi `ready_to_test`.
+    - **UPDATE status task** dari `development` menjadi `ready_to_test`.
     - Update field **"Last Updated"** dengan timestamp saat ini [YYYY-MM-DD HH:MM].
     - Tambahkan notes di field **"Notes"** jika ada informasi penting (misal: "Butuh environment variable X").
 

package/template/.agents/skills/pm/SKILL.md

@@ -49,7 +49,7 @@ description: Brief description of what this Skill does and when to use it
    ## Priority 0 (Critical)
 
    ### [TASK-000] Environment Setup
-   - **Spec:** `specification/000_spec_environment_setup.md`
+   - **Spec:** `specifications/000_spec_environment_setup.md`
    - **Status:** `not_started`
    - **Assigned To:** Developer Agent
    - **Dependencies:** None
@@ -62,7 +62,7 @@ description: Brief description of what this Skill does and when to use it
    ## Priority 1 (High)
 
    ### [TASK-001] User Authentication - Login
-   - **Spec:** `specification/001_spec_login.md`
+   - **Spec:** `specifications/001_spec_login.md`
    - **Status:** `not_started`
    - **Assigned To:** Developer Agent
    - **Dependencies:** TASK-000
@@ -75,7 +75,7 @@ description: Brief description of what this Skill does and when to use it
    ## Priority 2 (Medium)
 
    ### [TASK-XXX] [Nama Task]
-   - **Spec:** `specification/XXX_spec_...md`
+   - **Spec:** `specifications/XXX_spec_...md`
    - **Status:** `not_started`
    - **Assigned To:** -
    - **Dependencies:** TASK-XXX
@@ -88,7 +88,7 @@ description: Brief description of what this Skill does and when to use it
    ## Blocked Tasks
 
    ### [TASK-XXX] [Nama Task]
-   - **Spec:** `specification/XXX_spec_...md`
+   - **Spec:** `specifications/XXX_spec_...md`
    - **Status:** `blocked`
    - **Assigned To:** -
    - **Dependencies:** TASK-XXX
@@ -102,8 +102,8 @@ description: Brief description of what this Skill does and when to use it
    ## Completed Tasks
 
    ### [TASK-XXX] [Nama Task]
-   - **Spec:** `specification/XXX_spec_...md`
-   - **Status:** `human_validated`
+   - **Spec:** `specifications/XXX_spec_...md`
+   - **Status:** `done`
    - **Assigned To:** Developer Agent
    - **Dependencies:** TASK-XXX
    - **Description:** [Deskripsi singkat]
@@ -114,13 +114,11 @@ description: Brief description of what this Skill does and when to use it
 5. **STATUS DEFINITIONS:**
    Pastikan setiap task memiliki salah satu status berikut:
    - `not_started`: Task belum dikerjakan sama sekali
-   - `dev`: Task sedang dikerjakan oleh Developer Agent
-   - `fixing`: Task sedang diperbaiki oleh Fixer Agent
-   - `testing_ready`: Test scenario dari Tester Agent sudah dibuat
+   - `development`: Task sedang dikerjakan oleh Developer Agent
    - `ready_to_test`: Task sudah siap untuk dites (dev selesai, belum ada test scenario)
    - `testing`: Task sedang dites oleh Tester Agent
-   - `passed`: Task lolos test
-   - `failed`: Task tidak lolos test
+   - `fixing`: Task sedang diperbaiki oleh Fixer Agent
+   - `done`: Task lolos test
    - `human_validated`: Task sudah divalidasi oleh manusia (status ini diisi manual)
    - `blocked`: Task tidak dapat dikerjakan karena ada blocker
 
@@ -130,8 +128,8 @@ description: Brief description of what this Skill does and when to use it
    - Jika ada circular dependency, **TANDAI SEBAGAI BLOCKER** dan beri catatan.
 
 7. **MONITORING & UPDATES:**
-   - Ketika diminta update task list, baca ulang semua log di `logs/development/` untuk mengidentifikasi progress.
-   - Update status task berdasarkan log yang ditemukan.
+   - Ketika diminta update task list, baca ulang semua log di folder `task/` (terutama file `dev_log.md` dan `test_log.md` dalam subfolder masing-masing task) untuk mengidentifikasi progress.
+   - Update status task berdasarkan checklist di log yang ditemukan.
    - Update timestamp "Last Updated" setiap kali ada perubahan.
    - Update summary di bagian atas (Total Tasks, Completed, In Progress, etc).
 
@@ -164,9 +162,9 @@ description: Brief description of what this Skill does and when to use it
    ```
 
 9. **COLLABORATION WITH OTHER AGENTS:**
-   - **Developer Agent:** Akan update status dari `not_started` → `dev` → `ready_to_test`.
-   - **Fixer Agent:** Akan update status dari `failed` → `fixing` → `ready_to_test`.
-   - **Tester Agent:** Akan update status dari `ready_to_test` → `testing_ready` → `testing` → `passed`/`failed`.
+   - **Developer Agent:** Akan update status dari `not_started` → `development` → `ready_to_test`.
+   - **Fixer Agent:** Akan update status dari `fixing` → `ready_to_test`.
+   - **Tester Agent:** Akan update status dari `ready_to_test` → `testing` → `done`/`fixing`.
    - **Your Role:** Memastikan task list selalu up-to-date dan terorganisir dengan baik.
 
 10. **VALIDATION & QUALITY CHECK:**
@@ -185,7 +183,7 @@ Contoh input yang mungkin diterima:
 
 # Persistent Agent Memory
 
-You have a persistent Persistent Agent Memory directory at `/Users/admin/Development/study-indoensia/.claude/agent-memory/pman/`. Its contents persist across conversations.
+You have a persistent Persistent Agent Memory directory at `.claude/agent-memory/pman/`. Its contents persist across conversations.
 
 As you work, consult your memory files to build on previous experience. When you encounter a mistake that seems like it could be common, check your Persistent Agent Memory for relevant notes — and if nothing is written yet, record what you learned.
 

package/template/.claude/agents/analyst.md

@@ -1,6 +1,3 @@
----
-description: "System Analyst - mendefinisikan spesifikasi teknis dan infrastruktur proyek"
----
 **ACT AS:** Lead System Analyst & DevOps Architect.
 **CONTEXT:** Mendefinisikan spesifikasi teknis dan infrastruktur proyek.
 
@@ -10,9 +7,9 @@ description: "System Analyst - mendefinisikan spesifikasi teknis dan infrastrukt
 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.
@@ -55,7 +52,9 @@ description: "System Analyst - mendefinisikan spesifikasi teknis dan infrastrukt
 
 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]"
+## State Management
+> 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`