@ner076/prd-toolkit 0.1.4

package/skills/prd-generator/SKILL.md

@@ -0,0 +1,917 @@
+---
+name: prd-generator
+description: Transform a discovery-output.md into a complete auto-dev ready PRD with 16 sections including API contracts, data schemas, screen specs, and test scenarios. Use after prd-discovery completes. Output is ready to feed into Claude Code, Cursor, or Aider for automated implementation.
+---
+
+# PRD GENERATOR SKILL
+
+Skill untuk mengubah `discovery-output.md` menjadi **PRD lengkap yang auto-dev ready** — bisa langsung dipakai AI coding agent (Claude Code, Cursor, Copilot, Aider) untuk generate kode tanpa nyasar.
+
+**Input:** `discovery-output.md` dari `prd-discovery`.
+**Output:** `PRD-[nama-produk].md` — dokumen komprehensif dengan 13 section terstruktur.
+
+---
+
+# ROLE & PERSONA
+
+Anda adalah **Senior Technical PRD Writer** — spesialis menyusun PRD yang **eksplisit, terukur, dan tidak ambigu** untuk konsumsi AI coding agent.
+
+**Prinsip inti:**
+
+- **Explicit over implicit.** Setiap requirement punya ID, acceptance criteria, dan traceability.
+- **Contract over prose.** Utamakan tabel, schema, dan kontrak API. Prose hanya untuk konteks.
+- **No dangling assumption.** Kalau Discovery tidak cover, tulis eksplisit di section Assumptions — jangan mengarang di badan PRD.
+- **Design system as source of truth.** Component spec di PRD ini yang jadi acuan; tidak boleh ada UI decision di luar spec.
+
+---
+
+# INPUT VALIDATION
+
+Sebelum generate, validasi `discovery-output.md`:
+
+**Wajib ada:**
+- Section 1 (Product Context) — minimal Name, Description, Platform, Target User
+- Section 2 (Feature Backlog) — minimal 1 fitur dengan sub-fitur & AC
+- Section 5 (Data Model) — minimal 1 entitas dengan field
+- Section 7 (Design System) — minimal Tokens & 1 Component
+
+**Kalau ada yang kurang**, jangan generate. Tampilkan:
+
+> ⚠️ **Discovery output tidak lengkap.**
+>
+> Section yang kurang atau kosong:
+> - [list]
+>
+> Kembali ke `prd-discovery` untuk melengkapi, atau saya lanjutkan dengan asumsi best-practice untuk section yang kosong? Balas `lanjutkan` atau `kembali ke discovery`.
+
+Kalau user pilih `lanjutkan`, catat semua asumsi di Section 15 PRD.
+
+---
+
+# GENERATION FLOW
+
+1. **Baca** `discovery-output.md` sepenuhnya
+2. **Parse** ke internal structured data
+3. **Validate** kelengkapan
+4. **Announce** ke user:
+   > Discovery output ter-parse. Generating PRD dengan 13 section... Ini butuh beberapa saat.
+5. **Generate** file `PRD-[slug-nama-produk].md` dengan struktur di bawah
+6. **Present** file + ringkasan compact
+
+---
+
+# PRD STRUCTURE (13 SECTION WAJIB)
+
+Urutan tidak boleh diubah. Setiap section punya struktur eksplisit.
+
+```
+1.  Metadata & Overview
+2.  Product Context & Goals
+3.  Feature Map & Traceability
+4.  Functional Requirements (FR)
+5.  Non-Functional Requirements (NFR)
+6.  Detailed Feature Specification (per fitur)
+7.  Data Model
+8.  API Contracts
+9.  User Flows
+10. Architecture
+11. Design System Reference
+12. Screen-Level Specification
+13. Test Scenarios & Acceptance
+14. Deployment & Operations
+15. Assumptions, Risks, Open Questions
+16. Appendix — Traceability Matrix
+```
+
+*(16 total, tapi Metadata + Overview jadi Section 1 gabungan untuk kepraktisan)*
+
+---
+
+## SECTION 1 — Metadata & Overview
+
+```markdown
+# PRD: [Nama Produk]
+
+| Field | Value |
+|-------|-------|
+| Version | 1.0 (Draft) |
+| Generated | [tanggal] |
+| Source | discovery-output.md v[X] |
+| Status | Draft / Review / Final |
+| Author | AI PRD Generator |
+| Target Auto-Dev Compatibility | Claude Code / Cursor / Aider |
+```
+
+**Vision Statement** — 1-2 kalimat visi produk berdasarkan Product Context.
+
+**Executive Summary** — 3-5 bullet: apa yang dibangun, untuk siapa, masalah apa, differensiator, target scale.
+
+---
+
+## SECTION 2 — Product Context & Goals
+
+- **Problem Statement** — 2-3 kalimat, spesifik dengan dampak jika dibiarkan
+- **Target Audience**
+  - Primary persona: nama, karakteristik, pain points, goals
+  - Secondary persona (kalau ada)
+- **Success Metrics (KPI)** — minimal 4, terukur:
+  - Adoption metric (contoh: MAU, activation rate)
+  - Engagement metric (contoh: DAU/MAU ratio, retention W1/W4)
+  - Business metric (contoh: revenue per user, invoice/user/month)
+  - Quality metric (contoh: NPS, error rate)
+- **Non-Goals** — hal yang eksplisit **tidak** dikerjakan di v1 (penting biar auto-dev tidak nyasar)
+
+---
+
+## SECTION 3 — Feature Map & Traceability
+
+**Master Feature List** dengan ID:
+
+| Feature ID | Name | Category | Priority | Sub-Feature Count | Related |
+|-----------|------|----------|----------|-------------------|---------|
+| F-01 | Authentication | Core | Must | 6 | F-05, F-08 |
+| F-02 | Invoice Management | Core | Must | 11 | F-03, F-05 |
+| ... | | | | | |
+
+**Feature Dependency Diagram** — Mermaid `graph LR`:
+
+```mermaid
+graph LR
+    F01[F-01 Auth] --> F02[F-02 Invoice]
+    F01 --> F03[F-03 Client]
+    F02 --> F05[F-05 Notification]
+    F03 --> F02
+```
+
+**Aturan Mermaid untuk mencegah syntax error:**
+- Node ID: alphanumeric + underscore, no spaces
+- Label panjang: bungkus double quote
+- Edge label: `-- "text" -->`
+
+---
+
+## SECTION 4 — Functional Requirements (FR)
+
+Tabel lengkap dengan ID yang traceable:
+
+| FR ID | Feature | Sub-Feature | Requirement | Priority |
+|-------|---------|-------------|-------------|----------|
+| FR-01-01 | F-01 Auth | Login | Sistem harus mengizinkan user login dengan email + password | Must |
+| FR-01-02 | F-01 Auth | Login | Sistem harus rate-limit login gagal (5 attempt / 15 menit / IP) | Must |
+| FR-01-03 | F-01 Auth | Reset Password | Sistem harus kirim link reset ke email, expire 15 menit | Must |
+| FR-02-01 | F-02 Invoice | Create | User dapat create invoice dengan minimal 1 line item | Must |
+| ... | | | | |
+
+**Format ID:** `FR-[FeatureID]-[Sequence]`
+
+Setiap FR harus:
+- Punya 1 acceptance criteria (di Section 6, referenced by FR ID)
+- Terhubung ke minimal 1 API endpoint (di Section 8)
+- Terhubung ke minimal 1 test scenario (di Section 13)
+
+---
+
+## SECTION 5 — Non-Functional Requirements (NFR)
+
+Terstruktur per kategori. Semua **terukur**.
+
+**Performance**
+| NFR ID | Metric | Target | Measurement |
+|--------|--------|--------|-------------|
+| NFR-P-01 | API response time | p50 < 150ms, p95 < 300ms, p99 < 800ms | APM monitoring |
+| NFR-P-02 | Page load (TTI) | < 2s (3G Slow), < 1s (4G) | Lighthouse |
+| NFR-P-03 | Search query | < 200ms untuk dataset ≤ 10k rows | Query log |
+
+**Security**
+| NFR ID | Requirement | Implementation |
+|--------|-------------|----------------|
+| NFR-S-01 | Password hashing | bcrypt cost 12 minimum |
+| NFR-S-02 | Session token | JWT (15min) + refresh token (7d), stored httpOnly cookie |
+| NFR-S-03 | Rate limiting | Per IP + per user, sliding window |
+| NFR-S-04 | OWASP Top 10 | All mitigated, dokumentasi mitigation per item |
+| NFR-S-05 | Data-at-rest encryption | AES-256 untuk kolom sensitif (KTP, NPWP, dst) |
+| NFR-S-06 | Data-in-transit | TLS 1.3, HSTS enabled |
+
+**Scalability**
+| NFR ID | Requirement | Target |
+|--------|-------------|--------|
+| NFR-SC-01 | Concurrent user | 500 (v1), scalable to 5000 |
+| NFR-SC-02 | Database | Read replica ready, connection pooling |
+| NFR-SC-03 | Horizontal scaling | Stateless app, session di Redis |
+
+**Availability**
+| NFR ID | Requirement | Target |
+|--------|-------------|--------|
+| NFR-A-01 | Uptime SLA | 99.5% |
+| NFR-A-02 | RPO | 1 hour |
+| NFR-A-03 | RTO | 4 hours |
+| NFR-A-04 | Backup | Daily automated, retained 30 days |
+
+**Compliance** (kalau applicable)
+| NFR ID | Regulation | Requirement |
+|--------|-----------|-------------|
+| NFR-C-01 | UU PDP No.27/2022 | Consent record, data subject rights (access/rectify/delete/portability), breach notification 72 jam |
+| NFR-C-02 | Kominfo PSE | Registrasi PSE Lingkup Privat |
+| NFR-C-03 | POJK 11/2022 | (kalau produk fintech) |
+
+**Accessibility**
+| NFR ID | Requirement |
+|--------|-------------|
+| NFR-AC-01 | WCAG 2.1 Level AA |
+| NFR-AC-02 | Keyboard navigation semua interactive element |
+| NFR-AC-03 | Screen reader support (ARIA labels) |
+| NFR-AC-04 | Contrast ratio ≥ 4.5:1 (text normal), ≥ 3:1 (text large) |
+
+**Localization**
+| NFR ID | Requirement |
+|--------|-------------|
+| NFR-L-01 | Languages: [dari discovery] |
+| NFR-L-02 | Date format: locale-aware |
+| NFR-L-03 | Currency: multi-currency + display sesuai user pref |
+| NFR-L-04 | Timezone: user-selectable, default Asia/Jakarta |
+
+---
+
+## SECTION 6 — Detailed Feature Specification (Per Fitur)
+
+**Ini section paling tebal.** Per fitur (F-01, F-02, dst), tulis blok berikut:
+
+### F-XX — [Feature Name]
+
+**Description:** [1-2 paragraf]
+
+**Priority:** Must / Should / Could
+
+**Related Features:** F-XX, F-YY
+
+**User Stories:**
+- Sebagai [role], saya ingin [action] agar [outcome]
+- (minimal 2 story per fitur)
+
+**Sub-Features:**
+
+#### SF-XX-01 — [Sub-Feature Name]
+
+- **Priority:** Must
+- **Description:** ...
+- **Acceptance Criteria:**
+  - **AC-1** — Given [context], When [action], Then [outcome]
+  - **AC-2** — Given ..., When ..., Then ...
+- **Edge Cases:**
+  - EC-1: [skenario] → [expected behavior]
+  - EC-2: ...
+- **UI Reference:** Screen `SC-XX-01` (di Section 12)
+- **API Reference:** Endpoint `EP-XX-01` (di Section 8)
+- **Test Reference:** Scenario `TS-XX-01` (di Section 13)
+
+#### SF-XX-02 — ...
+
+*(ulangi semua sub-fitur)*
+
+**Business Rules Terkait:**
+- BR-01: ...
+- BR-02: ...
+
+**State Machine** (kalau fitur ber-status):
+```mermaid
+stateDiagram-v2
+    ...
+```
+
+**Transitions Table:**
+| From | To | Trigger | Guard | Side Effect |
+|------|----|----|--------|-----|
+| draft | sent | send() | items.length ≥ 1 && total > 0 | send email, log audit |
+| sent | overdue | scheduler | due_date < today && status != paid | queue reminder |
+
+---
+
+## SECTION 7 — Data Model
+
+### Entity Relationship Diagram (ERD)
+
+```mermaid
+erDiagram
+    User ||--o{ Invoice : "creates"
+    User ||--o{ Client : "manages"
+    Client ||--o{ Invoice : "receives"
+    Invoice ||--o{ InvoiceItem : "contains"
+    Invoice ||--o{ Payment : "settled_by"
+    
+    User {
+        uuid id PK
+        string email UK
+        string password_hash
+        string full_name
+        string role
+        timestamp created_at
+    }
+    Invoice {
+        uuid id PK
+        uuid user_id FK
+        uuid client_id FK
+        string invoice_number UK
+        date issue_date
+        date due_date
+        decimal subtotal
+        decimal tax_amount
+        decimal total
+        string currency
+        string status
+        text notes
+        timestamp created_at
+        timestamp updated_at
+    }
+```
+
+### Entity Detail
+
+**Untuk setiap entitas**, tulis blok berikut:
+
+#### Entity: [Name]
+
+**Table:** `snake_case_plural` (contoh: `invoices`)
+
+**Fields:**
+
+| Field | Type | Constraints | Default | Validation | Note |
+|-------|------|-------------|---------|------------|------|
+| id | UUID | PK, NOT NULL | `gen_random_uuid()` | - | - |
+| user_id | UUID | FK → users.id, NOT NULL | - | must exist | Owner |
+| invoice_number | VARCHAR(32) | UNIQUE, NOT NULL | auto | format `INV-YYYY-MM-NNNN` | Reset per bulan |
+| issue_date | DATE | NOT NULL | `CURRENT_DATE` | - | - |
+| due_date | DATE | NOT NULL | `issue_date + 30` | `>= issue_date` | - |
+| subtotal | DECIMAL(15,2) | NOT NULL | 0 | `>= 0` | Auto-calc |
+| tax_amount | DECIMAL(15,2) | NOT NULL | 0 | `>= 0` | Auto-calc |
+| total | DECIMAL(15,2) | NOT NULL | 0 | `= subtotal + tax - discount` | Computed |
+| status | ENUM | NOT NULL | 'draft' | draft/sent/paid/overdue/void | - |
+| currency | CHAR(3) | NOT NULL | 'IDR' | ISO 4217 | - |
+| notes | TEXT | NULL | NULL | max 1000 | - |
+| created_at | TIMESTAMPTZ | NOT NULL | `NOW()` | - | - |
+| updated_at | TIMESTAMPTZ | NOT NULL | `NOW()` | auto-update via trigger | - |
+| deleted_at | TIMESTAMPTZ | NULL | NULL | - | Soft delete |
+
+**Indexes:**
+- `idx_invoices_user_id` on (user_id)
+- `idx_invoices_client_id` on (client_id)
+- `idx_invoices_status` on (status)
+- `idx_invoices_due_date` on (due_date) — untuk overdue query
+- `unique_invoice_number` UNIQUE on (invoice_number)
+
+**Relations:**
+- `belongs_to` User (via user_id)
+- `belongs_to` Client (via client_id)
+- `has_many` InvoiceItem (via invoice_id)
+- `has_many` Payment (via invoice_id)
+
+**Triggers / Computed:**
+- `updated_at` auto-update on any change
+- `total` auto-recompute saat items berubah
+
+*(ulangi untuk semua entitas)*
+
+---
+
+## SECTION 8 — API Contracts
+
+**INI SANGAT PENTING untuk auto-dev.** Setiap FR yang butuh API harus punya endpoint spec eksplisit.
+
+**Base URL:** `https://api.[domain]/v1`
+
+**Auth:** `Authorization: Bearer <access_token>`
+
+**Response Envelope Standar:**
+```json
+{
+  "success": true,
+  "data": { ... },
+  "meta": { "pagination": { ... } },
+  "error": null
+}
+```
+
+**Error Envelope:**
+```json
+{
+  "success": false,
+  "data": null,
+  "error": {
+    "code": "VALIDATION_ERROR",
+    "message": "Human readable",
+    "details": [ { "field": "email", "issue": "invalid format" } ]
+  }
+}
+```
+
+**Error Codes Standar:**
+| HTTP | Code | Meaning |
+|------|------|---------|
+| 400 | `VALIDATION_ERROR` | Input tidak valid |
+| 401 | `UNAUTHORIZED` | Token missing/invalid |
+| 403 | `FORBIDDEN` | Tidak punya permission |
+| 404 | `NOT_FOUND` | Resource tidak ada |
+| 409 | `CONFLICT` | Business rule violation (contoh: invoice sudah paid) |
+| 422 | `UNPROCESSABLE` | Semantic error |
+| 429 | `RATE_LIMITED` | Rate limit exceeded |
+| 500 | `INTERNAL_ERROR` | Server error |
+
+### Endpoint Specification (Per Endpoint)
+
+Untuk setiap endpoint, tulis:
+
+#### EP-02-01 — Create Invoice
+
+- **Method:** POST
+- **Path:** `/invoices`
+- **Auth:** Required (Bearer token)
+- **Permission:** `invoice:create`
+- **Related FR:** FR-02-01
+
+**Request Body:**
+```json
+{
+  "client_id": "uuid",
+  "issue_date": "2026-07-06",
+  "due_date": "2026-08-05",
+  "currency": "IDR",
+  "notes": "string, optional, max 1000",
+  "items": [
+    {
+      "description": "string, required, max 200",
+      "quantity": "number, >0",
+      "unit_price": "number, >=0",
+      "discount_pct": "number, 0-100, optional",
+      "tax_pct": "number, 0-100, optional"
+    }
+  ]
+}
+```
+
+**Validation:**
+- `client_id` must exist and owned by user
+- `items` minimal 1, max 100
+- `due_date >= issue_date`
+- Sum of items amount > 0
+
+**Response 201:**
+```json
+{
+  "success": true,
+  "data": {
+    "id": "uuid",
+    "invoice_number": "INV-2026-07-0042",
+    "status": "draft",
+    "subtotal": 1000000,
+    "tax_amount": 110000,
+    "total": 1110000,
+    "created_at": "2026-07-06T10:00:00Z"
+  }
+}
+```
+
+**Possible Errors:**
+- 400 VALIDATION_ERROR — field validation failed
+- 403 FORBIDDEN — user tidak punya `invoice:create`
+- 404 NOT_FOUND — client_id tidak ada
+- 429 RATE_LIMITED
+
+**Side Effects:**
+- Insert row ke `invoices`, `invoice_items`
+- Log ke `audit_logs`
+- Emit event `invoice.created` ke queue
+
+*(ulangi untuk semua endpoint utama: list, get, update, delete, action-endpoints)*
+
+**Endpoint Inventory (ringkasan)**
+
+| Endpoint ID | Method | Path | FR | Permission |
+|-------------|--------|------|----|-----------|
+| EP-01-01 | POST | /auth/login | FR-01-01 | public |
+| EP-01-02 | POST | /auth/refresh | FR-01-04 | public |
+| EP-02-01 | POST | /invoices | FR-02-01 | invoice:create |
+| EP-02-02 | GET | /invoices | FR-02-02 | invoice:read |
+| EP-02-03 | GET | /invoices/:id | FR-02-03 | invoice:read |
+| EP-02-04 | PATCH | /invoices/:id | FR-02-04 | invoice:update |
+| EP-02-05 | POST | /invoices/:id/send | FR-02-05 | invoice:send |
+| EP-02-06 | POST | /invoices/:id/void | FR-02-06 | invoice:void |
+| ... | | | | |
+
+---
+
+## SECTION 9 — User Flows
+
+Per user journey utama, satu Mermaid flowchart.
+
+**Aturan Mermaid** (wajib untuk mencegah render error):
+- Node ID camelCase atau underscore, no spaces
+- Label > 20 char wajib dibungkus `"..."`
+- Gunakan `-->` atau `-- "label" -->`
+
+Untuk setiap flow:
+
+### UF-01 — [Nama Flow, contoh: Create & Send Invoice]
+
+**Persona:** [role]
+**Entry Point:** [halaman awal]
+**Goal:** [outcome]
+
+```mermaid
+flowchart TD
+    A["Dashboard"] --> B{"Klik Buat Invoice"}
+    B --> C["Form Create Invoice"]
+    C --> D["Isi Client + Items"]
+    D --> E{"Klik Simpan"}
+    E -- "Valid" --> F["Invoice Draft Tersimpan"]
+    E -- "Invalid" --> G["Tampil Error Inline"]
+    G --> D
+    F --> H{"Klik Kirim"}
+    H --> I["Konfirmasi Modal"]
+    I -- "Ya" --> J["Send Email + Status Sent"]
+    I -- "Batal" --> F
+```
+
+**Happy Path:** step-by-step (nomor)
+
+**Edge Cases:**
+- EC-1: Klien belum ada → CTA `+ Klien Baru` inline
+- EC-2: Item kosong → tombol Simpan disabled
+- EC-3: Email gagal terkirim → status tetap `draft`, tampilkan retry banner
+
+*(ulangi untuk flow utama)*
+
+---
+
+## SECTION 10 — Architecture
+
+**System Diagram:**
+
+```mermaid
+graph TD
+    Client["Web Client (Next.js)"] --> CDN["CDN / Edge"]
+    Client --> Gateway["API Gateway"]
+    Gateway --> Auth["Auth Service"]
+    Gateway --> App["App Service (API)"]
+    App --> DB[("PostgreSQL")]
+    App --> Cache[("Redis")]
+    App --> Queue["BullMQ"]
+    Queue --> Worker["Background Worker"]
+    Worker --> Email["Email Provider (SES/Resend)"]
+    Worker --> Storage["Object Storage (S3/R2)"]
+    App --> Storage
+    App --> Log["Log Aggregator (Loki)"]
+    App --> Metric["Metrics (Mimir)"]
+    App --> Trace["Traces (Tempo)"]
+```
+
+**Component Rationale:**
+| Component | Choice | Rationale |
+|-----------|--------|-----------|
+| Gateway | Nginx / Caddy | TLS termination, rate limit edge |
+| App | Node.js Fastify | Ecosystem TS, fast |
+| ... | | |
+
+**Bottleneck & Mitigation:**
+| Potential Bottleneck | Impact | Mitigation |
+|----------------------|--------|-----------|
+| PDF generation sync | Slow API response | Move to Worker via queue |
+| Search on large invoice list | Slow query | Add search index (pg_trgm) + Elasticsearch di v2 |
+| Email delivery burst | Rate limit provider | Batching + retry with backoff |
+
+---
+
+## SECTION 11 — Design System Reference
+
+**Copy dari `discovery-output.md` Section 7**, format ulang untuk PRD:
+
+### 11.1 Foundation
+- Component library: [shadcn/ui | MUI | ...]
+- Base framework: Tailwind CSS
+- Dark mode: enabled/disabled
+- Icon library: Lucide / Heroicons
+
+### 11.2 Design Tokens
+
+**Colors** — tabel lengkap dengan token name, HEX, usage
+**Typography** — tabel scale
+**Spacing** — scale value
+**Radius** — scale value
+**Shadow** — scale value
+**Motion** — duration + easing
+**Z-index scale** — modal, dropdown, tooltip, toast
+
+### 11.3 Component Specifications
+
+Per komponen, tabel spec lengkap (Button, Input, Textarea, Select, Checkbox, Radio, Toggle, Card, Modal, Drawer, Toast, Table, Badge, Avatar, Tabs, Tooltip, Dropdown Menu, Pagination, Empty State, Skeleton).
+
+**Format per component** (contoh Button):
+
+```markdown
+#### Button
+
+**Sizes:** sm (32px) / md (40px) / lg (48px)
+
+**Variants:**
+| Variant | BG | Text | Border | Use case |
+|---------|----|----|--------|----------|
+
+**States:** default, hover, active, focus, disabled, loading
+
+**Anatomy:** [icon-leading] · [label] · [icon-trailing]
+
+**Props (untuk implementation):**
+- `size`: 'sm' | 'md' | 'lg'
+- `variant`: 'primary' | 'secondary' | 'outline' | 'ghost' | 'destructive' | 'link'
+- `loading`: boolean
+- `disabled`: boolean
+- `iconLeading`: ReactNode
+- `iconTrailing`: ReactNode
+- `fullWidth`: boolean
+
+**Accessibility:**
+- `role="button"` (implisit dari `<button>`)
+- Keyboard: Space/Enter to activate
+- Loading state: `aria-busy="true"`
+- Disabled: `aria-disabled="true"`
+```
+
+### 11.4 Layout System
+- Breakpoints
+- Container max-width
+- Grid
+- Sidebar / Header / Footer dimensions
+- Content padding per breakpoint
+
+### 11.5 Iconography
+- Library, size scale, style (outline/solid), stroke width
+
+### 11.6 Content & Voice
+- Tone: [formal/casual/friendly]
+- Voice guidelines
+- Sentence case vs Title Case untuk labels
+
+---
+
+## SECTION 12 — Screen-Level Specification
+
+**Per screen**, blok berikut:
+
+### SC-XX-01 — [Screen Name, contoh: Invoice List]
+
+- **URL Path:** `/invoices`
+- **Layout Container:** AppShell (Header + Sidebar + Content)
+- **Access:** requires auth + `invoice:read`
+- **Related Feature:** F-02
+- **API used:** EP-02-02 (list), EP-02-06 (delete bulk)
+
+**Structure (top-to-bottom):**
+
+1. **Page Header**
+   - Title: `Invoice` (h1, weight 700, size 30px)
+   - Description: `Kelola semua invoice Anda` (body-sm, neutral-500)
+   - Action: Button primary md `+ Buat Invoice` → navigate `SC-02-03`
+
+2. **Filter Bar** (Card, padding 16px, mb 16px)
+   - Date range picker (default: last 30 days)
+   - Status multi-select (chip style)
+   - Search input (dengan icon leading, debounce 300ms)
+   - Button ghost `Reset filter` (kanan)
+
+3. **Bulk Action Bar** (muncul saat ≥1 row dicentang)
+   - Text: `[N] terpilih`
+   - Action buttons: `Export`, `Send Reminder`, `Delete` (destructive)
+
+4. **Data Table**
+   - Columns: `[checkbox]`, `Number`, `Client`, `Issue Date`, `Due Date`, `Total`, `Status` (Badge), `Actions` (Dropdown menu)
+   - Row height: 56px
+   - Hover: neutral-50 bg
+   - 10 rows per page
+   - Sortable columns: Issue Date, Due Date, Total
+
+5. **Pagination** (bottom, right-aligned)
+   - Info: `Menampilkan 1-10 dari 234`
+   - Controls: `< Prev`, page numbers, `Next >`
+
+**States:**
+- **Loading:** table skeleton 10 rows
+- **Empty (no data):** illustration + h2 `Belum ada invoice` + body `Buat invoice pertama Anda untuk mulai` + CTA `+ Buat Invoice`
+- **Empty (filtered):** copy `Tidak ada invoice sesuai filter` + link `Reset filter`
+- **Error:** fallback card + CTA `Coba lagi`
+
+**Responsive:**
+- **Mobile (<640px):**
+  - Table → Card list (1 kolom)
+  - Card: number, client, total, status, tanggal
+  - Filter → drawer di kanan, trigger dari button icon
+  - Bulk actions → sticky bottom bar
+- **Tablet (640-1023px):**
+  - Table dengan kolom terlipat (hide Client atau Issue Date)
+
+**Microcopy:**
+- Search placeholder: `Cari nomor invoice atau nama klien...`
+- Bulk delete confirm: `Hapus [N] invoice? Data yang dihapus bisa dipulihkan dari Trash selama 30 hari.`
+- Toast success: `[N] invoice berhasil dihapus.`
+- Toast error: `Gagal menghapus. Coba lagi.`
+
+*(ulangi untuk semua screen utama: List, Detail, Create, Edit)*
+
+---
+
+## SECTION 13 — Test Scenarios & Acceptance
+
+Format Gherkin (Given-When-Then) untuk setiap AC di Section 6, plus edge cases.
+
+### TS-02-01 — Create Invoice Happy Path
+
+**Related FR:** FR-02-01
+**Related Endpoint:** EP-02-01
+
+```gherkin
+Feature: Create Invoice
+
+  Scenario: Admin creates invoice with valid client and items
+    Given user is logged in as admin
+      And client "PT ABC" exists
+    When user navigates to /invoices/new
+      And selects client "PT ABC"
+      And adds line item {desc: "Design logo", qty: 1, price: 5000000}
+      And clicks "Simpan sebagai Draft"
+    Then invoice is saved with status "draft"
+      And invoice_number matches pattern "INV-YYYY-MM-####"
+      And subtotal is 5000000
+      And tax_amount is 550000 (11% PPN)
+      And total is 5550000
+      And user is redirected to invoice detail
+      And audit log entry is created
+```
+
+### TS-02-02 — Create Invoice Validation Errors
+
+```gherkin
+  Scenario: Create invoice without items
+    Given user is on /invoices/new
+      And client is selected
+    When user clicks "Simpan sebagai Draft" without adding items
+    Then submit button was disabled
+      And helper text "Minimal 1 item wajib diisi" is shown
+
+  Scenario: Create invoice with client not owned
+    Given user tries POST /invoices with client_id belonging to another user
+    Then response is 403 FORBIDDEN
+      And error.code is "FORBIDDEN"
+```
+
+*(ulangi untuk setiap sub-fitur — minimal 1 happy path + 2 edge case per sub-fitur)*
+
+---
+
+## SECTION 14 — Deployment & Operations
+
+**Environments:**
+| Env | Purpose | URL | Auto-deploy |
+|-----|---------|-----|-------------|
+| dev | Development | dev.[domain] | on push to `develop` |
+| staging | Pre-prod QA | staging.[domain] | on merge to `main` |
+| prod | Production | app.[domain] | manual approval |
+
+**CI/CD Pipeline:**
+```
+push → lint → typecheck → unit test → build → integration test → deploy dev
+                                                                    ↓
+                                                            promote → staging
+                                                                    ↓
+                                                            approval → prod
+```
+
+**Cloud Infrastructure:**
+- Provider: AWS
+- Region: `ap-southeast-3` (Jakarta) — untuk latency Indonesia
+- Compute: ECS Fargate atau EC2 (t3.medium min)
+- DB: RDS PostgreSQL Multi-AZ
+- Cache: ElastiCache Redis
+- Storage: S3 dengan lifecycle policy
+- CDN: CloudFront
+
+**Observability Stack:**
+- **Metrics:** Grafana Mimir (Prometheus-compatible)
+- **Logs:** Grafana Loki
+- **Traces:** Grafana Tempo
+- **Dashboard:** Grafana (LGTM stack)
+- **Alerting:** Grafana Alertmanager → Slack/PagerDuty
+
+**Key Alerts:**
+- API p95 > 500ms selama 5 menit
+- Error rate > 1% selama 5 menit
+- DB connection pool > 80% selama 3 menit
+- Queue depth > 1000 selama 5 menit
+- Disk usage > 80%
+
+**Runbooks:**
+- Deployment rollback: [1 kalimat prosedur]
+- Database restore: [1 kalimat]
+- Incident response: [link ke doc]
+
+**Secrets Management:**
+- AWS Secrets Manager / SSM Parameter Store
+- No secrets di git, no secrets di env file production
+
+---
+
+## SECTION 15 — Assumptions, Risks, Open Questions
+
+**Assumptions Made (karena Discovery tidak specify):**
+- A-01: Tax PPN 11% (standar Indonesia 2025+)
+- A-02: Default currency IDR
+- A-03: Session timeout 7 hari (refresh token)
+- A-04: [dst]
+
+**Risks:**
+| Risk ID | Description | Impact | Likelihood | Mitigation |
+|---------|-------------|--------|-----------|-----------|
+| R-01 | Email delivery rate limit di burst | High | Medium | Batching + fallback provider |
+| R-02 | PDF generation memory bloat | Medium | Low | Worker isolated + memory limit |
+| R-03 | Compliance PDP breach → sanksi | Very High | Low | Consent record + audit log + DPO |
+
+**Open Questions** (perlu keputusan tim sebelum implementasi):
+- Q-01: Apakah recurring invoice masuk MVP atau v2?
+- Q-02: Multi-tenancy strategy: row-level atau schema-per-tenant?
+- Q-03: [dst]
+
+---
+
+## SECTION 16 — Appendix: Traceability Matrix
+
+**Cross-reference table** untuk auditability:
+
+| Feature | Sub-Feature | FR | Endpoint | Screen | Test | AC |
+|---------|-------------|----|----|--------|------|-----|
+| F-02 | SF-02-01 Create | FR-02-01 | EP-02-01 | SC-02-03 | TS-02-01, TS-02-02 | AC-1, AC-2, AC-3 |
+| F-02 | SF-02-02 List | FR-02-02 | EP-02-02 | SC-02-01 | TS-02-03 | AC-1 |
+| ... | | | | | | |
+
+**Coverage check:**
+- Setiap FR punya endpoint ✅
+- Setiap FR punya screen ✅
+- Setiap FR punya test ✅
+
+Kalau ada gap, tulis di Open Questions.
+
+---
+
+# WRITING RULES (Wajib Ditegakkan)
+
+1. **Semua item punya ID.** FR-XX-YY, EP-XX-YY, SC-XX-YY, TS-XX-YY, dst. ID unik dan konsisten.
+2. **Tidak ada "dsb" atau "dan lain-lain"** untuk requirement — sebutkan eksplisit atau tulis di Open Questions.
+3. **Angka dan unit selalu eksplisit.** Bukan "cepat", tapi "< 300ms p95".
+4. **Setiap section minimal isi 3 baris substansial** (kecuali diagram).
+5. **Gunakan tabel** untuk requirement, endpoint, field, spec. Prose hanya untuk konteks.
+6. **Kata perintah untuk requirement:** "harus", "wajib", "must" — tidak boleh "sebaiknya", "diharapkan".
+7. **Format Mermaid** — patuhi aturan node ID no-spaces, long labels wajib di-quote.
+8. **Sync antara section** — kalau FR-02-01 disebutkan, harus ada di Section 4 DAN referenced di Section 6, 8, 13.
+9. **No lorem ipsum, no placeholder text.** Kalau data tidak ada, tulis eksplisit di Assumptions.
+
+---
+
+# CLOSING PROTOCOL
+
+Setelah PRD selesai di-generate:
+
+1. Tulis file `PRD-[slug-nama-produk].md` di working directory
+2. Tampilkan ringkasan kompak (maksimal 10 baris) ke user:
+
+> ✅ **PRD selesai.**
+>
+> - **File:** `PRD-[slug].md` ([X] KB, ~[Y] halaman ekuivalen)
+> - **Sections:** 16
+> - **Requirements:** [N] FR, [N] NFR
+> - **Endpoints:** [N]
+> - **Screens:** [N]
+> - **Test scenarios:** [N]
+> - **Assumptions dicatat:** [N]
+> - **Open questions:** [N]
+>
+> **Rekomendasi langkah selanjutnya:**
+> 1. Review Section 15 (Open Questions) bersama tim
+> 2. Validasi Section 5 (NFR) dengan infrastructure engineer
+> 3. Siap di-feed ke Claude Code / Cursor sebagai context
+
+3. Present file ke user via `present_files`
+
+---
+
+# QUALITY CHECKLIST (WAJIB dijalankan sebelum output final)
+
+Sebelum menyerahkan PRD ke user, verifikasi internal:
+
+- [ ] Semua 16 section terisi (tidak ada yang kosong / lorem)
+- [ ] Setiap FR punya endpoint di Section 8
+- [ ] Setiap FR punya screen di Section 12
+- [ ] Setiap FR punya test di Section 13
+- [ ] Setiap entitas di Section 7 punya minimal 1 endpoint yang mengaksesnya
+- [ ] Semua Mermaid diagram lolos aturan syntax
+- [ ] Setiap state machine punya transition table
+- [ ] Semua NFR punya angka spesifik (bukan "cepat", "banyak")
+- [ ] Traceability Matrix di Section 16 lengkap
+- [ ] Tidak ada "TBD" di badan PRD — kalau ada, pindah ke Section 15 Open Questions
+- [ ] Design token dan component spec di Section 11 konsisten dengan Screen spec di Section 12
+
+Kalau ada gagal check, perbaiki sebelum output.