---
name: ipb-ppki-v4-writing-standard
description: Workflow for drafting undergraduate theses (PA) following the IPB University Scientific Writing Guidelines (PPKI) Edition 4.
trigger: When drafting any section of the Final Project (PA) for IPB University.
---

# IPB PPKI v4 Writing Standard

## Overview
This skill ensures that all academic writing is strictly aligned with the PPKI Edition 4 guidelines, focusing on structural integrity, academic tone, and citation precision to minimize revision cycles.

## Core Principles
1. **Alignment-First:** Every section must map back to the research questions and objectives.
2. **Evidence-First:** No technical claim without a reference ID or empirical data.
3. **Academic Objectivity:** Strictly avoid first-person pronouns (I, we, my). Use passive voice or objective phrasing.
4. **Structural Rigor:** Adherence to the standard IPB chapter sequence.

## Standard Structure (The Blueprint)

### Halaman Depan (Preliminary Pages) — Romawi (i, ii, iii…)
1. **Halaman Judul** — Logo IPB, judul (14pt bold kapital), nama/NIM, program studi, tahun
2. **Lembar Pengesahan** — Tanda tangan: Pembimbing, Ketua Prodi, Ketua Penguji, Anggota Penguji (+ NIP)
3. **Lembar Pernyataan Orisinalitas** — Surat bebas plagiat, ditandatangani di atas materai
4. **Abstrak (ID)** — ≤250 kata: tujuan, metode, hasil, kesimpulan. Kata kunci 3–5 kata
5. **Abstract (EN)** — Terjemahan abstrak. Keywords 3–5 kata
6. **Kata Pengantar** — Ucapan terima kasih terstruktur
7. **Daftar Isi / Gambar / Tabel / Lampiran** — Auto-generated

### Isi Utama (Body) — Arab (1, 2, 3…)
- **Bab I. Pendahuluan**
  - 1.1 Latar Belakang (The "Why": Problem $\rightarrow$ Current Gap $\rightarrow$ Proposed Solution)
  - 1.2 Rumusan Masalah
  - 1.3 Tujuan (Specific, Measurable, Achievable)
  - 1.4 Manfaat
  - 1.5 Batasan Penelitian
  - 1.6 Sistematika Penulisan
- **Bab II. Tinjauan Pustaka**
  - State-of-the-art review. Organized logically from general to specific.
  - Tabel penelitian terdahulu (min. 5).
- **Bab III. Materi dan Metode**
  - 3.1 Waktu dan Tempat
  - 3.2 Alat dan Bahan (Detailed specs)
  - 3.3 Prosedur Penelitian/Perancangan (The "How": Architecture, Flowcharts, Equations)
  - 3.4 Analisis Data (How results will be validated)
- **Bab IV. Hasil dan Pembahasan**
  - Results (What happened) $\rightarrow$ Discussion (Why it happened & Comparison with literature).
- **Bab V. Kesimpulan dan Saran**
  - Direct answers to the objectives in Bab I.

### Halaman Belakang (End Matter)
- Daftar Pustaka (format IPB PPKI v4 — **bukan APA**. Lihat `references/ipb-citation-format.md` untuk aturan lengkap. Gunakan CSL `ipb.csl` dari `https://github.com/auriza/csl-ipb` atau `ipb_en.csl` untuk versi Inggris.)
- Lampiran (source code, datasheet, foto, dokumentasi)
- Riwayat Hidup

### Format Sitasi & Referensi
Aturan sitasi dan daftar pustaka mengikuti format IPB PPKI Edisi 4 (bukan APA). Lihat `references/ipb-citation-format.md` untuk panduan lengkap meliputi:
- Sitasi dalam teks per jumlah penulis
- Format daftar pustaka per tipe sumber (jurnal, buku, prosiding, tesis, dll)
- Aturan umum (urutan abjad, sentence case vs title case, DOI, URL)
- Penulisan metadata di Zotero/Mendeley
- Instalasi CSL IPB

**CSL resmi:** `https://github.com/auriza/csl-ipb` — gunakan file `ipb.csl` (Bahasa Indonesia) atau `ipb_en.csl` (Bahasa Inggris).

### LaTeX Template
A ready-to-use LaTeX project template is maintained at `/home/faiz034/TA-LaTeX/`. See `references/latex-format-specs.md` untuk aturan format LaTeX lengkap dan `references/dotx-to-latex-mapping.md` untuk detail konversi resmi IPB .dotx → LaTeX. Copy dari template ini daripada menulis dari awal.

### Biblatex IPB Citation Overrides
Untuk mendekati format daftar pustaka IPB PPKI v4 menggunakan biblatex (style APA sebagai basis), lihat `references/biblatex-ipb-overrides.md` untuk macro override spesifik, pitfall yang diketahui, dan hasil kepatuhan ~85-90%. Untuk 100% presisi IPB, gunakan Zotero + CSL `ipb.csl` dan export ke plain text.

**TeX Live Debian**: `bahasa.ldf` / `indonesian.ldf` TIDAK tersedia. Pakai `[english]` + `\addto\captionsenglish{\renewcommand{\chaptername}{Bab}}`. CSL processor juga tidak terinstall.

### Academic Writing Orchestration
For full thesis writing (all chapters, research-to-draft pipeline), the **Executive Executor** framework (`executive-executor` skill) provides orchestration with a specialized `agent-academic` that writes chapters in LaTeX following PPKI v4 standards. The Executor handles research mining → design → chapter writing → compilation. Use the Executor for end-to-end thesis drafting; use this skill (ipb-ppki-v4) for individual section/chapter editing, style checking, or when the user only needs writing guidance without orchestration.

### BibTeX Reference Management
For merging BibTeX/RIS exports (from Zotero/Mendeley) into `pustaka.bib` — including cross-check, deduplication, gap analysis, and merge — see `references/bibtex-management-workflow.md` for the complete workflow (parsing, key generation, filtering, formatting, verification).

### File Delivery for Reference Files
When the user asks to send `.bib` or other reference files via Telegram: consult the `hermes-file-delivery` skill PROACTIVELY before attempting delivery. Key gotchas: `.bib` is not a supported Telegram extension (rename to `.txt`), files must be under allowed cache roots (`~/.hermes/document_cache/` for documents), and MEDIA: delivery should be verified — don't assume success. Copy → rename → verify existence → then send.

### Google Docs → LaTeX Reconstruction
When the user has existing drafts in Google Docs, follow the reconstruction workflow: read the Doc via API, then rewrite from scratch in LaTeX (never copy-paste verbatim). See `references/gdocs-to-latex-workflow.md` for the step-by-step process including OAuth auth, citation mapping to BibTeX, and LaTeX formatting conventions.

### Writing Specification Document
A comprehensive Markdown writing guide (`SPECS.md`) is maintained alongside the LaTeX template. See `references/specs-document-summary.md` for a summary. When the user asks about thesis format rules, structure, or checklists, refer to or send this document.

## Writing Checklist & Guardrails
- [ ] **Tone Check:** No "Aku", "Saya", "Kami". Replace with "Penelitian ini...", "Sistem dirancang...", "Dilakukan pengujian...".
- [ ] **Citation Check:** Every technical claim has a citation in the format required by PPKI v4 (IPB-specific, NOT generic APA). See `references/ipb-citation-format.md` for detailed rules. Use CSL file `ipb.csl` from `https://github.com/auriza/csl-ipb` for Mendeley/Zotero.
- [ ] **Figure/Table Check:** All figures/tables are numbered, captioned, and cited in the text *before* they appear.
- [ ] **Consistency Check:** Terminology (e.g., "Severity Index") is consistent throughout the document.
- [ ] **Engineering Logic Flow:** Ensure the flow follows: Requirement $\rightarrow$ Design $\rightarrow$ Implementation $\rightarrow$ Verification.

## Engineering-Style Writing Patterns (Granular Decomposition)
For technical projects, avoid narrative descriptions. Use a decomposed approach:
1. **Requirement Mapping:** Start sections with a "Functional Requirement" table (e.g., latency, accuracy, dose thresholds).
2. **Modular Breakdown:** Describe the system as independent modules (e.g., Perception $\rightarrow$ Transmission $\rightarrow$ Actuation).
3. **Verification Pairing:** Every design choice in Bab III must have a corresponding test/verification in Bab IV.

## Verification Steps
1. Cross-reference the current draft section with the corresponding PPKI v4 chapter requirement.
2. Verify that the logical flow follows: Problem $\rightarrow$ Method $\rightarrow$ Result $\rightarrow$ Conclusion.
3. Audit citations against the Master Reference Table.

## Document Triangulation Protocol (Critical)
When the user provides multiple documents (proposal, plan files, visualizers, notebooks), NEVER assume which version is authoritative. Follow this protocol:
1. **Read ALL provided documents** before drafting anything.
2. **Identify version conflicts** — e.g., proposal says Linear Mapping (T=SI×K), plan_logic.md says volume-based 5-step, HTML visualizer says V5 with PSF + tank selection + clamping.
3. **Ask the user which version to use** before drafting. Do not guess.
4. **Default rule**: The most recently shared document (e.g., HTML visualizer shared after proposal) is likely the current evolved state, but always confirm.
5. **Memory vs. documents**: When memory conflicts with a freshly provided document, the document wins. Update memory accordingly.

## Writing Approach: Reconstruction, Not Copy-Paste

When the user has existing drafts (Google Docs, previous LaTeX, notes), the preferred approach is **reconstruction** — rewriting from scratch with full understanding, not copy-pasting. This produces better academic writing because:

1. The writer re-engages with the logic and argument flow
2. Sentences are restructured for the target format (LaTeX, formal academic)
3. Gaps in reasoning become visible during rewriting
4. The final text has consistent voice and style

**Protocol when user has existing drafts:**
1. Read the existing draft(s) to understand the technical content
2. Identify the key claims, data points, and argument structure
3. **Rewrite from scratch** in the target format, preserving technical accuracy but reconstructing the prose
4. Flag any claims that need citations or evidence checks
5. Never copy-paste paragraphs verbatim — always re-express

This applies to all chapters (Bab I–V). Even when the source draft is well-written, the act of reconstruction improves alignment with PPKI v4 structure and IPB formatting rules.

## Multi-Iteration Drafting Warning
For engineering projects, the system logic often evolves across multiple iterations (proposal → plan → implementation → visualizer). Each draft iteration costs context and time. To minimize wasted cycles:
- Always ask "Is this the latest version of the logic?" before drafting methodology sections.
- Check for HTML visualizers, Jupyter notebooks, or firmware files that may contain the ground truth.
- When in doubt, present the user with the conflicting versions and ask them to pick.