name: legacy-decoder
description: Reverse-engineer legacy code into structured documentation (Tech Spec + Tasks). Use when: user says "pahami kode", "analisis legacy", "reverse engineer", "mapping kode", "dokumentasi kode existing".
SKILL: LEGACY DECODER
📋 Metadata
- Nama: Legacy Decoder
- Versi: 1.0
- Output: Analisis arsitektur + Tech Spec (opsional) + Task List
- Lokasi File:
.agents/4-LEGACY-DECODER.md
- Dependensi: Tidak ada (bekerja dari kode existing)
🎯 Trigger Keywords
- "Pahami kode"
- "Analisis legacy"
- "Reverse engineer"
- "Mapping kode"
- "Dokumentasi kode existing"
- "Baca legacy code"
- "Review codebase"
- "Baca hasil analisis"
- "Load legacy analysis"
📂 Baca/Menyimpan File
- Baca:
@.agents/4-LEGACY-DECODER.md
- Simpan:
.agents/4-LEGACY-DECODER.md
- Output Tech Spec:
.agents/2-TECH-SPEC.md (opsional)
- Output Tasks:
.agents/3-TASKS.md
⚙️ Cara Kerja Skill
FASE 0: Deteksi Trigger
- Jika user bilang "baca" atau "load" → Baca
.agents/4-LEGACY-DECODER.md dan beri ringkasan.
- Jika user bilang "pahami", "analisis", "reverse", "mapping", atau "review" → Lanjut ke FASE 1.
FASE 1: Discovery
- Scan struktur folder project
- Baca file konfigurasi (
package.json, composer.json, pyproject.toml, go.mod, Cargo.toml, Gemfile, pubspec.yaml, CMakeLists.txt, pom.xml, dll.)
- Identifikasi framework, runtime, database, dan dependency utama
- Simpan ringkasan stack + struktur folder ke
.agents/4-LEGACY-DECODER.md (append)
FASE 2: Codebase Mapping
- Petakan struktur direktori (controller/model/service/route/view)
- Identifikasi entry point dan alur request
- Simpan dependency graph / arsitektur tingkat tinggi ke
.agents/4-LEGACY-DECODER.md (append)
FASE 3: Business Logic Extraction
- Ekstrak daftar routes/endpoints/actions
- Identifikasi entities/models utama dan relasinya
- Catat business rules yang terlihat dari kode
- Simpan ringkasan business logic ke
.agents/4-LEGACY-DECODER.md (append)
FASE 4: Database Reverse (jika ada DB)
- Baca migration files / schema definition
- Petakan entity-relationship
- Catat index, constraint, trigger
- Simpan database overview ke
.agents/4-LEGACY-DECODER.md (append)
FASE 5: Output Generation
Setelah FASE 1-4 selesai dan semua tersimpan:
Opsional — Tech Spec (2-TECH-SPEC.md):
- Tanyakan: "Buat Tech Spec dari hasil analisis? (y/n)"
- Jika ya → generate 5 bagian (Tech Stack, DB Design, Interface, Alur, Keamanan)
- Simpan ke
.agents/2-TECH-SPEC.md
Wajib — Tasks (3-TASKS.md):
- Generate task list berdasarkan temuan (refactor, bug fix, optimasi, dokumentasi)
- Simpan ke
.agents/3-TASKS.md
FASE 6: Finalisasi
- Tampilkan ringkasan hasil analisis
- Rekomendasikan lanjut ke implement-task atau verify