Legislative Briefer

• 89 enacted BAAs — full text at ~/Vault/bangsamoro/bangsamoro-laws/BAA-{N}.md (11 categories: governance, budget, health, education, economy, peace, local govt, electoral, social welfare, symbols, environment)
• 554 adopted resolutions — full text at ~/Vault/bangsamoro/bangsamoro-resolutions/resolution{N}.md
• BDP 2023-2028 — 14 chapters with macroeconomic targets and sector goals at ~/Vault/bangsamoro/bangsamoro-development/bdp-2023-2028/
• Cross-reference map — BDP Goals ↔ Supporting BAAs ↔ BDP Chapters ↔ Key Resolutions
• Use /bangsamoro Workflow A (BAA by topic) for Section II impact assessment context
• Use /bangsamoro Workflow C (BDP targets) for Section II development alignment
• Use /bangsamoro Workflow D (cross-reference) for Section XIII strategic intelligence

Verification Protocol

This skill follows the Universal Verification Framework (Prevent → Detect → Confirm). Read ~/.gemini/skills/fact-checker/references/verification-framework.md for the full protocol. Read ~/.gemini/skills/fact-checker/references/source-preload-protocol.md — MANDATORY: load source text BEFORE writing any citation. No claims from training data when local source exists. If a claim cannot be verified against loaded source files, mark it [UNVERIFIED] — never guess or fabricate. See source-preload-protocol.md Section 4.

Before writing (PREVENT):

1. Invoke /bangsamoro to load domain context
2. Read the fact-check error log at ~/Vault/skill-outputs/fact-checker/fact-check-error-log.md
3. Fast research: check for recent developments on the topic (new BAAs, leadership changes, court rulings)
4. Read authoritative reference files relevant to the topic
5. Build a Fact Sheet from verified sources — sole source of truth for writing
6. Include Fact Sheet + fabrication warnings in all subagent prompts

After writing (DETECT): Invoke /fact-checker on the complete document. The enhanced fact-checker runs P1-P10 checks automatically.

Before publishing (CONFIRM): Present the fact-check report to the user. Fix all CRITICAL and HIGH errors. Regenerate output only after report is clean.

For complex legislative process diagrams or stakeholder maps, use /excalidraw to create visual aids for the briefer. For visual legislative analysis summaries and one-page visual briefs, use /visualize to generate self-contained HTML visualizations that can be converted to PNG for embedding.

Pre-Draft Interview

Before starting the workflow, resolve these critical inputs. Scan the user's initial prompt — if they already provided an answer, skip that question. Present all unanswered questions in a single batch with your recommended answer for each.

Rules:

• Ask ALL missing questions at once — never one at a time
• For each question, provide your recommended answer based on available context
• If the user's prompt clearly answers all 6, skip the interview entirely and proceed to the Workflow
• Maximum 2 rounds of clarification — after that, proceed with best judgment and mark assumptions as [ASSUMED: ...]
• The briefer is only valuable when tailored to a specific MP's priorities — if MP info is missing after 2 rounds, draft with generic BARMM development priorities and flag sections needing personalization

Workflow

Draft the briefer in batches, awaiting user approval between each:

Section III (Previous Proceedings) is skipped unless explicitly requested — this comes from the user's personal records and session notes.

After completing each batch, ask the user if they want to continue to the next batch.

Section Guide Reference

Read references/csw-section-guides.md for detailed objectives, content requirements, and format specifications for each of the 13 sections. That reference contains the complete CSW framework. Key highlights:

Language requirements:

• Sections IX, XII: Draft in Tagalog or Taglish (for plenary delivery)
• Section X: Tagalog for plenary, English/Taglish for committee deliberations
• All other sections: English (formal analytical prose)

Section X format (Interpellation Q&A):

INTRODUCTION: [Context / "HUGOT"]
QUESTION: [Clear, concise]
ANTICIPATED ANSWER: [With citation]
MANIFESTATION: [Follow-up statement]
PROPOSED AMENDMENT (if applicable): [Intent to propose]
JUSTIFICATION: [Why it improves the measure]

Section XII structure (1-Minute Yes Vote): Opening declaration → Key benefits (2-3 sentences) → Link to MP priorities → Bangsamoro impact → Legislative process acknowledgment → BARMM alignment → Memorable slogan → Call to action. Target: 150-300 words.

BARMM Agencies

Read /bangsamoro skill's references/moa-structure.md for the complete BARMM agency hierarchy (at ~/.gemini/skills/bangsamoro/references/moa-structure.md). For quick reference, the 16 executive units are: OCM + 15 line ministries (MAFAR, MBHTE, MENRE, MFBM, MOH, MHSD, MIPA, MILG, MOLE, MPOS, MPW, MOST, MSSD, MTIT, MOTC). Only cite agencies from BAA No. 13.

Legal Citations

Follow /legal-assistant/references/citation-guide.md for all citation formats. Key rules for briefers:

• Philippine law: Cite inline by specific provision (BOL, Art. XII, Sec. 9). Full citation on first mention.
• Islamic jurisprudence (Sections VII and II): Express in general legislative terms. Place exact Qur'an/Hadith sources in footnotes with Arabic text and English translation. See the citation guide for exact format.
• Source attribution: Include Source: [file path] when extracting verbatim provisions.

PDF Footnote Rendering: When the document will be rendered as PDF, footnotes must appear on a separate page with a 'Footnotes' heading — never inline after chapter text. Ensure the footnotes markdown extension is enabled in generate-pdf.py, and the guidebook-template.html has page-break-before: always on the .footnote class. See /guidebook-writer build-pipeline.md for the full CSS pattern.

Edge Cases and Fallbacks

Forum Briefing Template

When the user requests a briefer for a Bangsamoro Leaders' Forum — or any executive-legislative dialogue event — use this specialized output template instead of the standard 13-section CSW format.

Trigger phrases: "forum briefing", "leaders' forum", "BLF", "bangsamoro leaders forum", "forum flow", "executive-legislative forum", "provincial governors forum"

Forum Briefing Structure

BANGSAMORO LEADERS' FORUM BRIEFING PACKAGE
[Forum Title] | [Date] | [Venue]
Prepared by: [Office/Staff] | Cleared by: [CoS/Supervisor]

---

SECTION 1: RATIONALE AND OPENING

Purpose of the forum — why convene, what decisions or inputs are expected.
Opening protocol: invocation, Islamic greeting, national/regional anthem (if applicable),
introduction of forum chair and presiding officer.
Background context: what led to this forum, what is at stake.

---

SECTION 2: PARLIAMENTARY REPORT

Legislative accomplishments presented to LGU executives:
- Bills passed (with BAA numbers, short titles, and brief descriptions)
- Resolutions adopted (highlight those with direct LGU impact)
- Bills filed and pending (organized by committee)
- Committee activities (hearings conducted, position papers received)
- Interpellation outcomes / floor amendments of note

Format: table with columns — Measure | Status | LGU Impact | For Action By

---

SECTION 3: EXECUTIVE AGENDA PRESENTATION

Items from the Bangsamoro Government (OCM/Ministries) for presentation to LGU leaders:
- Policy directions aligned with the Mas Matatag na Bangsamoro Agenda (5 pillars)
- Programs and projects with LGU partnership requirements
- Budget allocations (block grants, special funds, LGU shares)
- Directives or MCs for LGU compliance
- Issues requiring joint executive-legislative-LGU action

Format: per pillar or per presenting ministry, with Q&A note for each item.

---

SECTION 4: OPEN FORUM (Q&A WITH LGU EXECUTIVES)

Pre-draft anticipated questions from LGU executives (provincial governors, mayors,
municipal councilors) based on pending legislative agenda and known LGU concerns.

For each anticipated question:
- QUESTION: [From: Governor/Mayor of ___]
- ISSUE: [Legislative or executive concern]
- PREPARED RESPONSE: [Who responds + talking points]
- ACTION: [If commitment is needed: COMMIT / DEFER / REFER to ___]

---

SECTION 5: PROVINCIAL IMPRESSIONS

Space for recording impressions and commitments per province:
- Maguindanao del Norte / Maguindanao del Sur
- Lanao del Sur
- Basilan
- Sulu
- Tawi-Tawi
- Cotabato City / Special Geographic Area

For each: key concern raised, commitment made, follow-up responsibility, deadline.

---

SECTION 6: CLOSING DIRECTIVES

Summary of action items from the forum:
- Commitments made by Parliament (bills to fast-track, hearings to schedule)
- Commitments made by OCM/Ministries (programs to activate, funds to release)
- LGU action items (ordinances to enact, reports to submit, programs to implement)
- Next forum schedule or follow-up mechanism

Closing protocol: synthesis remarks by forum chair, closing prayer/du'aa.

When to Use Forum Briefing vs. Standard Briefer

Complexity Tiers

Determine the tier at Setup based on the measure type. If unsure, ask.

Examples

Read references/examples.md for annotated examples of key sections — including good-vs-weak interpellation questions, a sample 1-Minute Yes Vote in Tagalog, and an Overview format.

Research

Use Gemini CLI tools to ground every section in evidence:

• /bangsamoro — FIRST source for all BARMM context. Use its 4 legislative lookup workflows:
  • Workflow A: Find related BAAs by topic (89 enacted, categorized by 11 domains)
  • Workflow B: Find related resolutions by theme (554 transcribed, classified by 13 categories)
  • Workflow C: Find BDP targets for the bill's sector (14 chapters with quantified targets)
  • Workflow D: Cross-reference BAAs ↔ BDP Goals ↔ Resolutions for strategic context
• Read — Load the measure being analyzed in full context (1M window advantage). Load related BAAs at ~/Vault/bangsamoro/bangsamoro-laws/BAA-{N}.md and resolutions at ~/Vault/bangsamoro/bangsamoro-resolutions/resolution{N}.md
• Grep/Glob — Search ~/Vault/bangsamoro/bangsamoro-laws/INDEX.md, ~/Vault/bangsamoro/bangsamoro-resolutions/INDEX.md, docs/Bills/INDEX.md for keyword matches
• WebSearch — Current data, statistics, expert opinions for impact assessment (check local sources first)
• /legal-assistant — Verify every legal citation

Output

Save the completed briefer as a .md file. Offer .docx conversion via /docx skill for formal submission.

Gotchas

• Never cite guidebooks or draft documents as primary sources for factual claims — trace back to enacted law (BAA, RA, BOL, BDP)
• BDP chapter numbers may shift between editions — verify against ~/Vault/bangsamoro/bangsamoro-development/bdp-2023-2028/
• If the model is answering from memory about BOL article numbers, BAA provisions, or official titles, it is in extrinsic mode — force intrinsic mode by loading source documents before citing
• Shari'ah compliance analysis requires loading actual Islamic jurisprudence sources, not relying on training data generalizations
• Gender mainstreaming analysis must reference specific BARMM gender-related BAAs and resolutions, not generic frameworks
• The 13-section CSW format is mandatory — never skip or merge sections even when content seems thin

Subagent Honesty Rules

Every subagent prompt dispatched by this skill MUST include this footer:

HONESTY RULES:

1. Only extract values explicitly stated in source documents. If ambiguous or missing, leave blank with a one-line reason.
2. A wrong answer is 3x worse than a blank answer. When in doubt, leave it blank.
3. Tag every factual claim as EXTRACTED (with source reference) or INFERRED (with evidence). Inferred claims will be verified first.

Fact-Check Before Delivery

Before delivering the final briefer, run /fact-checker on the output. Legislative briefers are dense with verifiable facts — bill numbers, committee assignments, official names and titles, constitutional provisions, budget figures. An MP reading from a briefer with wrong facts on the plenary floor is a serious problem. The fact-checker verifies all claims and produces a report.