القائمة
Implement Satu Sehat Kobar evidence upload + verification and the auto-filled bidirectional journal. Use for EPIC-06 and EPIC-07 issues (duty-travel domain).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when updating `docs/prd`, adding or revising Mermaid diagrams, synchronizing AI-ready issue docs/templates, or aligning `README.md`, `AGENTS.md`, and root docs with the latest active Satu Sehat Kobar PRD package and MVP scope.
Implement Satu Sehat Kobar end-to-end/UAT tests, the consolidated UAT/demo seed (17 roles + full sample flow), and the deployment + smoke + rollback runbook. Use for EPIC-16 issues.
Implement Satu Sehat Kobar backend & integration foundations — inter-plugin service contracts (SC-01..11), cross-plugin domain events / cache invalidation, notification channel abstraction, external integration adapter boundary, shared API middleware, observability, and migration ordering. Use for EPIC-14 issues.
Implement Satu Sehat Kobar master-data foundation — official/local region, health facilities, organization units, document numbering, signatories, holidays, transport, and personnel (employees/positions/supervisors). Use for EPIC-13 issues (addenda doc 21/22/23).
Implement the Satu Sehat Kobar duty-travel approval engine — DB-configured multi-step chain, finance auto-skip, finance ABAC scope, in-app notifications, return/reject, and the approver queue. Use for EPIC-04 issues.
Implement the Satu Sehat Kobar dashboard aggregate endpoint with KV caching and the 12-indicator SPM tracker. Use for EPIC-08 issues (satusehat-dashboard / spm-health).
| name | sskobar-evidence-journal |
| description | Implement Satu Sehat Kobar evidence upload + verification and the auto-filled bidirectional journal. Use for EPIC-06 and EPIC-07 issues (duty-travel domain). |
Domain of plugin duty-travel. Builds on sskobar-data-d1 + sskobar-api-rbac. Authoritative: docs/prd/04, docs/prd/05, docs/prd/10, docs/prd/12 (DEC-012/013), docs/prd/17 (PII).
duty_evidence (...participant_user_id, evidence_type, file_url, file_hash, classification, status, verified_by, verified_at, notes). Enums: evidence_type (laporan_tugas|foto_kegiatan|daftar_hadir|tiket|kwitansi|lainnya), classification (public|internal|confidential).duty_request_participants may upload their own evidence (DEC-012). POST /duty-requests/:id/evidence multipart → R2, compute SHA-256, notify verifier.classification required. confidential ⇒ UI warning; classified files need permission evidence.view_classified. PII scan is manual + warning in Phase 1 (AI in Phase 2).POST /duty-evidence/:id/verify (→verified) / /return (→returned, notes required), notify participant.verified, set duty_requests.status='evidence_verified' (audited).duty_journals (...completion_status, summary, evidence_ids_json). Enum completion_status: pending|completed|returned.completed when all of the user's evidence is verified; evidence_ids_json lists related evidence.pending; re-verified ⇒ completed. Every transition audited.GET /journals/export?format=csv|xlsx&period=... (filter unit/period/status). List GET /journals?... paginated (default 20, max 100), newest first.