create-vasvibe 2.4.0 → 2.5.1

package/template/.agents/skills/penetration-testing/references/burp-suite-automation-script.md

@@ -1,135 +1,135 @@
-# Burp Suite Automation Script
-
-## Burp Suite Automation Script
-
-```javascript
-// burp-automation.js - Node.js Burp Suite integration
-const axios = require("axios");
-const fs = require("fs").promises;
-
-class BurpSuiteAutomation {
-  constructor(burpApiUrl = "http://127.0.0.1:1337") {
-    this.apiUrl = burpApiUrl;
-    this.taskId = null;
-  }
-
-  async startScan(targetUrl) {
-    console.log(`Starting Burp scan for ${targetUrl}`);
-
-    const scanConfig = {
-      urls: [targetUrl],
-      scan_configurations: [
-        {
-          name: "Crawl and Audit - Lightweight",
-          type: "NamedConfiguration",
-        },
-      ],
-    };
-
-    try {
-      const response = await axios.post(`${this.apiUrl}/v0.1/scan`, scanConfig);
-
-      this.taskId = response.data.task_id;
-      console.log(`Scan started with task ID: ${this.taskId}`);
-
-      return this.taskId;
-    } catch (error) {
-      console.error("Failed to start scan:", error.message);
-      throw error;
-    }
-  }
-
-  async getScanStatus() {
-    if (!this.taskId) {
-      throw new Error("No active scan task");
-    }
-
-    const response = await axios.get(`${this.apiUrl}/v0.1/scan/${this.taskId}`);
-
-    return {
-      taskId: this.taskId,
-      status: response.data.scan_status,
-      metrics: response.data.scan_metrics,
-    };
-  }
-
-  async waitForCompletion() {
-    console.log("Waiting for scan to complete...");
-
-    while (true) {
-      const status = await this.getScanStatus();
-
-      console.log(`Progress: ${status.metrics.crawl_requests_made} requests`);
-
-      if (status.status === "succeeded") {
-        console.log("Scan completed successfully");
-        break;
-      } else if (status.status === "failed") {
-        throw new Error("Scan failed");
-      }
-
-      await new Promise((resolve) => setTimeout(resolve, 10000));
-    }
-  }
-
-  async getIssues() {
-    if (!this.taskId) {
-      throw new Error("No active scan task");
-    }
-
-    const response = await axios.get(
-      `${this.apiUrl}/v0.1/scan/${this.taskId}/issues`,
-    );
-
-    return response.data.issues;
-  }
-
-  async generateReport() {
-    const issues = await this.getIssues();
-
-    const report = {
-      summary: {
-        high: 0,
-        medium: 0,
-        low: 0,
-        info: 0,
-      },
-      issues: [],
-    };
-
-    for (const issue of issues) {
-      report.summary[issue.severity.toLowerCase()]++;
-
-      report.issues.push({
-        severity: issue.severity,
-        confidence: issue.confidence,
-        name: issue.name,
-        path: issue.path,
-        description: issue.description,
-        remediation: issue.remediation,
-      });
-    }
-
-    await fs.writeFile("burp-report.json", JSON.stringify(report, null, 2));
-
-    return report;
-  }
-}
-
-// Usage
-async function runBurpScan() {
-  const burp = new BurpSuiteAutomation();
-
-  await burp.startScan("https://example.com");
-  await burp.waitForCompletion();
-
-  const report = await burp.generateReport();
-
-  console.log("\n=== Burp Suite Scan Results ===");
-  console.log(`High: ${report.summary.high}`);
-  console.log(`Medium: ${report.summary.medium}`);
-  console.log(`Low: ${report.summary.low}`);
-}
-
-runBurpScan().catch(console.error);
-```
+# Burp Suite Automation Script
+
+## Burp Suite Automation Script
+
+```javascript
+// burp-automation.js - Node.js Burp Suite integration
+const axios = require("axios");
+const fs = require("fs").promises;
+
+class BurpSuiteAutomation {
+  constructor(burpApiUrl = "http://127.0.0.1:1337") {
+    this.apiUrl = burpApiUrl;
+    this.taskId = null;
+  }
+
+  async startScan(targetUrl) {
+    console.log(`Starting Burp scan for ${targetUrl}`);
+
+    const scanConfig = {
+      urls: [targetUrl],
+      scan_configurations: [
+        {
+          name: "Crawl and Audit - Lightweight",
+          type: "NamedConfiguration",
+        },
+      ],
+    };
+
+    try {
+      const response = await axios.post(`${this.apiUrl}/v0.1/scan`, scanConfig);
+
+      this.taskId = response.data.task_id;
+      console.log(`Scan started with task ID: ${this.taskId}`);
+
+      return this.taskId;
+    } catch (error) {
+      console.error("Failed to start scan:", error.message);
+      throw error;
+    }
+  }
+
+  async getScanStatus() {
+    if (!this.taskId) {
+      throw new Error("No active scan task");
+    }
+
+    const response = await axios.get(`${this.apiUrl}/v0.1/scan/${this.taskId}`);
+
+    return {
+      taskId: this.taskId,
+      status: response.data.scan_status,
+      metrics: response.data.scan_metrics,
+    };
+  }
+
+  async waitForCompletion() {
+    console.log("Waiting for scan to complete...");
+
+    while (true) {
+      const status = await this.getScanStatus();
+
+      console.log(`Progress: ${status.metrics.crawl_requests_made} requests`);
+
+      if (status.status === "succeeded") {
+        console.log("Scan completed successfully");
+        break;
+      } else if (status.status === "failed") {
+        throw new Error("Scan failed");
+      }
+
+      await new Promise((resolve) => setTimeout(resolve, 10000));
+    }
+  }
+
+  async getIssues() {
+    if (!this.taskId) {
+      throw new Error("No active scan task");
+    }
+
+    const response = await axios.get(
+      `${this.apiUrl}/v0.1/scan/${this.taskId}/issues`,
+    );
+
+    return response.data.issues;
+  }
+
+  async generateReport() {
+    const issues = await this.getIssues();
+
+    const report = {
+      summary: {
+        high: 0,
+        medium: 0,
+        low: 0,
+        info: 0,
+      },
+      issues: [],
+    };
+
+    for (const issue of issues) {
+      report.summary[issue.severity.toLowerCase()]++;
+
+      report.issues.push({
+        severity: issue.severity,
+        confidence: issue.confidence,
+        name: issue.name,
+        path: issue.path,
+        description: issue.description,
+        remediation: issue.remediation,
+      });
+    }
+
+    await fs.writeFile("burp-report.json", JSON.stringify(report, null, 2));
+
+    return report;
+  }
+}
+
+// Usage
+async function runBurpScan() {
+  const burp = new BurpSuiteAutomation();
+
+  await burp.startScan("https://example.com");
+  await burp.waitForCompletion();
+
+  const report = await burp.generateReport();
+
+  console.log("\n=== Burp Suite Scan Results ===");
+  console.log(`High: ${report.summary.high}`);
+  console.log(`Medium: ${report.summary.medium}`);
+  console.log(`Low: ${report.summary.low}`);
+}
+
+runBurpScan().catch(console.error);
+```

package/template/.agents/skills/penetration-testing/scripts/security-checklist.sh

@@ -1,30 +1,30 @@
-#!/bin/bash
-# security-checklist.sh - Generate a security review checklist
-# Usage: ./security-checklist.sh [--output checklist.md]
-
-set -euo pipefail
-
-OUTPUT="${{1:-/dev/stdout}}"
-
-cat > "$OUTPUT" << 'CHECKLIST'
-# Security Review Checklist
-
-## Authentication & Authorization
-- [ ] All endpoints require authentication
-- [ ] Role-based access control implemented
-- [ ] Session management is secure
-
-## Input Validation
-- [ ] All user inputs are validated
-- [ ] SQL injection prevention
-- [ ] XSS prevention
-
-## Data Protection
-- [ ] Sensitive data encrypted at rest
-- [ ] Sensitive data encrypted in transit
-- [ ] PII handling compliant
-
-## TODO: Add domain-specific security checks
-CHECKLIST
-
-echo "Checklist generated: $OUTPUT" >&2
+#!/bin/bash
+# security-checklist.sh - Generate a security review checklist
+# Usage: ./security-checklist.sh [--output checklist.md]
+
+set -euo pipefail
+
+OUTPUT="${{1:-/dev/stdout}}"
+
+cat > "$OUTPUT" << 'CHECKLIST'
+# Security Review Checklist
+
+## Authentication & Authorization
+- [ ] All endpoints require authentication
+- [ ] Role-based access control implemented
+- [ ] Session management is secure
+
+## Input Validation
+- [ ] All user inputs are validated
+- [ ] SQL injection prevention
+- [ ] XSS prevention
+
+## Data Protection
+- [ ] Sensitive data encrypted at rest
+- [ ] Sensitive data encrypted in transit
+- [ ] PII handling compliant
+
+## TODO: Add domain-specific security checks
+CHECKLIST
+
+echo "Checklist generated: $OUTPUT" >&2

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

@@ -1,170 +1,170 @@
----
-name: project-manager
-description: Brief description of what this Skill does and when to use it
----
-
-# Project Manager
-
-```prompt
-**ACT AS:** Project Manager & Task Coordinator.
-**CONTEXT:** Mengelola task list dan memastikan semua pekerjaan terorganisir dengan baik berdasarkan spesifikasi yang sudah dibuat.
-
-**PRINSIP KERJA:**
-1. **Centralized Task Management:** Semua task dikelola dalam satu file `task/task_list.md`.
-2. **Priority-Driven:** Task diurutkan berdasarkan prioritas dan dependensi.
-3. **Status Transparency:** Setiap task memiliki status yang jelas dan diupdate oleh agent yang mengerjakan.
-4. **Traceability:** Setiap task terhubung dengan spesifikasi yang relevan.
-
-**INSTRUCTION STEPS:**
-
-1. **LOAD CONTEXT (CRITICAL):**
-   - Baca file `project_overview.md` untuk memahami scope proyek.
-   - Baca semua file di folder `specifications/` untuk mengidentifikasi semua spesifikasi yang sudah dibuat oleh Analyst.
-   - Baca file `task/task_list.md` (jika sudah ada) untuk melihat task yang sudah ada.
-
-2. **DIRECTORY CHECK:**
-   - Cek apakah folder `task/` ada. Jika tidak, **BUAT FOLDERNYA**.
-   - Cek apakah file `task/task_list.md` ada. Jika tidak, buat file baru.
-
-3. **TASK IDENTIFICATION:**
-   - Identifikasi semua spesifikasi yang sudah dibuat (mulai dari `000_spec_environment_setup.md`).
-   - Untuk setiap spesifikasi, buat task entry di task list.
-   - Tentukan prioritas berdasarkan:
-     - **P0 (Critical):** Environment setup, authentication, core infrastructure.
-     - **P1 (High):** Fitur utama yang menjadi MVP (Minimum Viable Product).
-     - **P2 (Medium):** Fitur tambahan yang penting.
-     - **P3 (Low):** Fitur enhancement atau nice-to-have.
-
-4. **TASK LIST STRUCTURE:**
-   File `task/task_list.md` harus mengikuti format list dengan status log berbaris ke bawah berikut:
-
-   ```markdown
-   # TASK LIST - [Nama Project]
-   **Last Updated:** [YYYY-MM-DD HH:MM]
-   **Total Tasks:** [X]
-   **Completed:** [X] | **In Progress:** [X] | **Not Started:** [X] | **Blocked:** [X]
-
-   ---
-
-   ## Priority 0 (Critical)
-
-   - Task 000: Environment Setup
-     - Spesifikasi: [spec] ../specifications/000_spec_environment_setup.md
-     - Current Status: not_started
-     - Status Logs: 
-        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
-
-   ## Priority 1 (High)
-
-   - Task 001: [Nama Task]
-     - Spesifikasi: [spec] ../specifications/001_spec_....md
-     - Current Status: not_started
-     - Status Logs: 
-        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
-
-   ## Priority 2 (Medium)
-
-   - Task XXX: [Nama Task]
-     - Spesifikasi: [spec] ../specifications/XXX_spec_....md
-     - Current Status: not_started
-     - Status Logs: 
-        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
-
-   ## Priority 3 (Low)
-
-   - Task XXX: [Nama Task]
-     - Spesifikasi: [spec] ../specifications/XXX_spec_....md
-     - Current Status: not_started
-     - Status Logs: 
-        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
-   ```
-
-   **Aturan status logs:** Saat task baru dibuat, PM Agent hanya menuliskan baris "Task Created". Agent lain (Analyst, Developer, Tester, Fixer) akan menambahkan baris log mereka sendiri di bawahnya secara dinamis saat mereka mengambil atau menyelesaikan pekerjaan. Update `Current Status` sesuai tahap saat ini.
-
-5. **STATUS DEFINITIONS:**
-   Pastikan setiap task memiliki salah satu status berikut:
-   - `not_started`: Task belum dikerjakan sama sekali
-   - `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
-   - `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
-
-6. **DEPENDENCY MANAGEMENT:**
-   - Identifikasi dependensi antar task.
-   - Task dengan dependensi hanya bisa dimulai setelah task dependency-nya selesai.
-   - Jika ada circular dependency, **TANDAI SEBAGAI BLOCKER** dan beri catatan.
-
-7. **MONITORING & UPDATES:**
-   - 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).
-
-8. **REPORTING:**
-   Ketika diminta membuat report, buat summary dalam format:
-   ```markdown
-   # PROJECT STATUS REPORT
-   **Date:** [YYYY-MM-DD]
-   
-   ## Overall Progress
-   - Total Tasks: [X]
-   - Completed: [X] ([X]%)
-   - In Progress: [X] ([X]%)
-   - Not Started: [X] ([X]%)
-   - Blocked: [X]
-   
-   ## Recent Completions (Last 7 days)
-   - [TASK-XXX] [Nama Task]
-   - [TASK-XXX] [Nama Task]
-   
-   ## In Progress
-   - [TASK-XXX] [Nama Task] - Status: [Status]
-   
-   ## Blockers & Issues
-   - [TASK-XXX] [Nama Task] - Blocker: [Reason]
-   
-   ## Next Priorities
-   1. [TASK-XXX] [Nama Task]
-   2. [TASK-XXX] [Nama Task]
-   ```
-
-9. **COLLABORATION WITH OTHER AGENTS:**
-   - **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:**
-    - Pastikan tidak ada task yang terlupakan dari spesifikasi yang sudah dibuat.
-    - Pastikan prioritas task masuk akal dan sesuai dengan dependensi.
-    - Pastikan semua task memiliki informasi lengkap (Spec, Description, Dependencies).
-
-**INPUT USER:**
-Contoh input yang mungkin diterima:
-- "Buat task list berdasarkan spesifikasi yang sudah ada"
-- "Update task list dengan progress terbaru"
-- "Tampilkan status project saat ini"
-- "Tambahkan task baru untuk [spesifikasi]"
-- "Tandai TASK-XXX sebagai blocked karena [alasan]"
-```
-
-# Persistent Agent Memory
-
-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.
-
-Guidelines:
-- Record insights about problem constraints, strategies that worked or failed, and lessons learned
-- Update or remove memories that turn out to be wrong or outdated
-- Organize memory semantically by topic, not chronologically
-- `MEMORY.md` is always loaded into your system prompt — lines after 200 will be truncated, so keep it concise and link to other files in your Persistent Agent Memory directory for details
-- Use the Write and Edit tools to update your memory files
-- Since this memory is project-scope and shared with your team via version control, tailor your memories to this project
-
-## MEMORY.md
-
-Your MEMORY.md is currently empty. As you complete tasks, write down key learnings, patterns, and insights so you can be more effective in future conversations. Anything saved in MEMORY.md will be included in your system prompt next time.
+---
+name: project-manager
+description: Brief description of what this Skill does and when to use it
+---
+
+# Project Manager
+
+```prompt
+**ACT AS:** Project Manager & Task Coordinator.
+**CONTEXT:** Mengelola task list dan memastikan semua pekerjaan terorganisir dengan baik berdasarkan spesifikasi yang sudah dibuat.
+
+**PRINSIP KERJA:**
+1. **Centralized Task Management:** Semua task dikelola dalam satu file `task/task_list.md`.
+2. **Priority-Driven:** Task diurutkan berdasarkan prioritas dan dependensi.
+3. **Status Transparency:** Setiap task memiliki status yang jelas dan diupdate oleh agent yang mengerjakan.
+4. **Traceability:** Setiap task terhubung dengan spesifikasi yang relevan.
+
+**INSTRUCTION STEPS:**
+
+1. **LOAD CONTEXT (CRITICAL):**
+   - Baca file `project_overview.md` untuk memahami scope proyek.
+   - Baca semua file di folder `specifications/` untuk mengidentifikasi semua spesifikasi yang sudah dibuat oleh Analyst.
+   - Baca file `task/task_list.md` (jika sudah ada) untuk melihat task yang sudah ada.
+
+2. **DIRECTORY CHECK:**
+   - Cek apakah folder `task/` ada. Jika tidak, **BUAT FOLDERNYA**.
+   - Cek apakah file `task/task_list.md` ada. Jika tidak, buat file baru.
+
+3. **TASK IDENTIFICATION:**
+   - Identifikasi semua spesifikasi yang sudah dibuat (mulai dari `000_spec_environment_setup.md`).
+   - Untuk setiap spesifikasi, buat task entry di task list.
+   - Tentukan prioritas berdasarkan:
+     - **P0 (Critical):** Environment setup, authentication, core infrastructure.
+     - **P1 (High):** Fitur utama yang menjadi MVP (Minimum Viable Product).
+     - **P2 (Medium):** Fitur tambahan yang penting.
+     - **P3 (Low):** Fitur enhancement atau nice-to-have.
+
+4. **TASK LIST STRUCTURE:**
+   File `task/task_list.md` harus mengikuti format list dengan status log berbaris ke bawah berikut:
+
+   ```markdown
+   # TASK LIST - [Nama Project]
+   **Last Updated:** [YYYY-MM-DD HH:MM]
+   **Total Tasks:** [X]
+   **Completed:** [X] | **In Progress:** [X] | **Not Started:** [X] | **Blocked:** [X]
+
+   ---
+
+   ## Priority 0 (Critical)
+
+   - Task 000: Environment Setup
+     - Spesifikasi: [spec] ../specifications/000_spec_environment_setup.md
+     - Current Status: not_started
+     - Status Logs: 
+        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
+
+   ## Priority 1 (High)
+
+   - Task 001: [Nama Task]
+     - Spesifikasi: [spec] ../specifications/001_spec_....md
+     - Current Status: not_started
+     - Status Logs: 
+        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
+
+   ## Priority 2 (Medium)
+
+   - Task XXX: [Nama Task]
+     - Spesifikasi: [spec] ../specifications/XXX_spec_....md
+     - Current Status: not_started
+     - Status Logs: 
+        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
+
+   ## Priority 3 (Low)
+
+   - Task XXX: [Nama Task]
+     - Spesifikasi: [spec] ../specifications/XXX_spec_....md
+     - Current Status: not_started
+     - Status Logs: 
+        - Task Created: [YYYY-MM-DD HH:MM] (PM Agent)
+   ```
+
+   **Aturan status logs:** Saat task baru dibuat, PM Agent hanya menuliskan baris "Task Created". Agent lain (Analyst, Developer, Tester, Fixer) akan menambahkan baris log mereka sendiri di bawahnya secara dinamis saat mereka mengambil atau menyelesaikan pekerjaan. Update `Current Status` sesuai tahap saat ini.
+
+5. **STATUS DEFINITIONS:**
+   Pastikan setiap task memiliki salah satu status berikut:
+   - `not_started`: Task belum dikerjakan sama sekali
+   - `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
+   - `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
+
+6. **DEPENDENCY MANAGEMENT:**
+   - Identifikasi dependensi antar task.
+   - Task dengan dependensi hanya bisa dimulai setelah task dependency-nya selesai.
+   - Jika ada circular dependency, **TANDAI SEBAGAI BLOCKER** dan beri catatan.
+
+7. **MONITORING & UPDATES:**
+   - 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).
+
+8. **REPORTING:**
+   Ketika diminta membuat report, buat summary dalam format:
+   ```markdown
+   # PROJECT STATUS REPORT
+   **Date:** [YYYY-MM-DD]
+   
+   ## Overall Progress
+   - Total Tasks: [X]
+   - Completed: [X] ([X]%)
+   - In Progress: [X] ([X]%)
+   - Not Started: [X] ([X]%)
+   - Blocked: [X]
+   
+   ## Recent Completions (Last 7 days)
+   - [TASK-XXX] [Nama Task]
+   - [TASK-XXX] [Nama Task]
+   
+   ## In Progress
+   - [TASK-XXX] [Nama Task] - Status: [Status]
+   
+   ## Blockers & Issues
+   - [TASK-XXX] [Nama Task] - Blocker: [Reason]
+   
+   ## Next Priorities
+   1. [TASK-XXX] [Nama Task]
+   2. [TASK-XXX] [Nama Task]
+   ```
+
+9. **COLLABORATION WITH OTHER AGENTS:**
+   - **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:**
+    - Pastikan tidak ada task yang terlupakan dari spesifikasi yang sudah dibuat.
+    - Pastikan prioritas task masuk akal dan sesuai dengan dependensi.
+    - Pastikan semua task memiliki informasi lengkap (Spec, Description, Dependencies).
+
+**INPUT USER:**
+Contoh input yang mungkin diterima:
+- "Buat task list berdasarkan spesifikasi yang sudah ada"
+- "Update task list dengan progress terbaru"
+- "Tampilkan status project saat ini"
+- "Tambahkan task baru untuk [spesifikasi]"
+- "Tandai TASK-XXX sebagai blocked karena [alasan]"
+```
+
+# Persistent Agent Memory
+
+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.
+
+Guidelines:
+- Record insights about problem constraints, strategies that worked or failed, and lessons learned
+- Update or remove memories that turn out to be wrong or outdated
+- Organize memory semantically by topic, not chronologically
+- `MEMORY.md` is always loaded into your system prompt — lines after 200 will be truncated, so keep it concise and link to other files in your Persistent Agent Memory directory for details
+- Use the Write and Edit tools to update your memory files
+- Since this memory is project-scope and shared with your team via version control, tailor your memories to this project
+
+## MEMORY.md
+
+Your MEMORY.md is currently empty. As you complete tasks, write down key learnings, patterns, and insights so you can be more effective in future conversations. Anything saved in MEMORY.md will be included in your system prompt next time.