GAAB Budget Analysis Skill

No training data for budget claims. Every peso amount must come from a GAAB file, BAA-13, or the e-Bangsamoro .ts files. If an amount cannot be sourced, mark it [UNVERIFIED].

For batch operations (creating 300+ program files), Steps 2-5 can be combined per agent — but Step 3 (validate) must still happen before the file is written. Each agent should grep-verify at least the TOTAL appropriation amount for each entity it processes.

Critical Rules

These exist because they were violated and caused rework:

1. Check INDEX.md first. Before claiming any BAA exists or doesn't exist, read legislation/baas/INDEX.md. BAA-56 IS the FY 2024 GAAB (P98.5B). It was missed once because the index wasn't checked. Never again.

2. All amounts verbatim. Every peso figure must be copied exactly from the source GAAB. Never round, estimate, or calculate amounts from training data.

3. All 7 fiscal years. FY 2020 through FY 2026. There is NO gap — FY 2024 exists (BAA-56).

4. Cross-year indicator matrices, not per-year tables. Performance indicators go in ONE matrix with FY columns, not separate tables per year. This is the format that was validated.

5. TOTAL row after last FY. Every budget table ends with a TOTAL row summing PS, MOOE, CO, and Overall Total across all years the program existed.

Source Files

All in the transcriptions repo at /Users/saidamenmambayao/apps/transcriptions/:

GAABs (7 enacted appropriations acts)

Other Sources

Output Directories

Mode 1: MINISTRY — Ministry Budget Index

Create or update a ministry-level budget index file.

Structure

# [Entity Name] — Budget Program Index

## Summary

| Fiscal Year | BAA | PS | MOOE | CO | Total |
|---|---|---:|---:|---:|---:|
| FY 2020 | BAA-3 | [amt] | [amt] | [amt] | [amt] |
| FY 2021 | BAA-15 | [amt] | [amt] | [amt] | [amt] |
| FY 2022 | BAA-23 | [amt] | [amt] | [amt] | [amt] |
| FY 2023 | BAA-32 | [amt] | [amt] | [amt] | [amt] |
| FY 2024 | BAA-56 | [amt] | [amt] | [amt] | [amt] |
| FY 2025 | BAA-65 | [amt] | [amt] | [amt] | [amt] |
| FY 2026 | BAA-85 | [amt] | [amt] | [amt] | [amt] |
| **TOTAL** | | **[sum]** | **[sum]** | **[sum]** | **[sum]** |

## I. General Administration and Support
[PS/MOOE/CO/Total per year table]

## II. Support to Operations
[PS/MOOE/CO/Total per year table]

## III. Operations
[PS/MOOE/CO/Total per year table]

### Sub-programs under Operations

#### [Sub-program Name]
[Per-year detail table]

### Cross-Year Sub-Program Matrix (Totals)

| Sub-Program | FY 2020 | FY 2021 | FY 2022 | FY 2023 | FY 2024 | FY 2025 | FY 2026 |
|---|---:|---:|---:|---:|---:|---:|---:|
| [name] | [total] | [total] | ... |
*First appeared: FY [year]. [Name changes noted.]*

## Performance Indicators
[Cross-year matrix — see Mode 2 format]

## Notes
- Structural changes across years
- Program name changes
- Entities spun off or absorbed

---
**Sources:** BAA-3, BAA-15, BAA-23, BAA-32, BAA-56, BAA-65, BAA-85
**Compiled:** YYYY-MM-DD

Process

1. Read INDEX.md at legislation/baas/INDEX.md to confirm all 7 GAABs exist
2. For each GAAB, search for the ministry section (e.g., "MINISTRY OF HEALTH" or "X. MINISTRY OF HEALTH")
3. Extract the "Appropriations, by Program" table — this gives GAS/STO/Operations with PS/MOOE/CO/Total
4. Extract all sub-programs under Operations — every named program with its budget
5. Extract performance indicators from the ORGANIZATIONAL OUTCOMES section (where present)
6. Check the e-Bangsamoro .ts file for FY 2024 indicators
7. Build cross-year matrices tracking each sub-program across all 7 FYs
8. Note structural changes — programs appearing, disappearing, renamed, reclassified

Entities (36 total)

• 1 BTA + 1 OCM + 15 Ministries + 11 Executive Offices/Commissions + 8 Special Purpose Funds

For entities not yet established in earlier FYs, mark as "Not yet established."

Mode 2: PROGRAM — Individual Program Budget File

Create a budget file for a single program across all fiscal years.

Template

The validated template is at: bangsamoro-government/program-budgets/tiyakap-bangsamoro-kalusugan-program.md

Always read this file before creating any new program budget file.

Structure

# [Program Name]

**Implementing MOA:** [Ministry/Office name and acronym]
**Parent Program:** [e.g., Operations > Access to Promotive Health Care Service]
**First Appeared:** FY [year] (BAA-[number])

## Program Description

[From special provisions or GAAB text. If none: "No formal description in GAAB text."]

## Program Budget Over the Years

| Fiscal Year | BAA | PS | MOOE | CO | Total |
|---|---|---:|---:|---:|---:|
| FY 2020 | BAA-3 | [amt or —] | ... |
| ... all 7 FYs ... |
| **TOTAL** | | **[sum PS]** | **[sum MOOE]** | **[sum CO]** | **[sum Total]** |

### Year-over-Year Change

| Period | Change | % Change |
|---|---:|---:|
| FY 2021 -> FY 2022 | [amt] | [%] |

## Performance Indicators Over the Years

[Attribution notes if needed]

### Outcome Indicators

| Indicator | FY 2020 | FY 2021 | FY 2022 | FY 2023 | FY 2024 | FY 2025 | FY 2026 |
|---|---|---|---|---|---|---|---|
| [indicator] | [target or —] | ... |

**Notes:**
[Explain reclassifications, name changes, discontinuations]

### Output Indicators

| Indicator | FY 2020 | FY 2021 | FY 2022 | FY 2023 | FY 2024 | FY 2025 | FY 2026 |
|---|---|---|---|---|---|---|---|
| **[Category]** | | | | | | | |
| [indicator] | [target or —] | ... |

**Notes:**
[Same]

### Key Indicator Evolution
[3-4 bullet summary of how indicators changed across years]

## Special Provisions Over the Years

| Fiscal Year | BAA | Provision |
|---|---|---|
| FY [year] | BAA-[n] | [verbatim provision text] |

---
**Sources:** [list BAAs where program appears]
**Compiled:** YYYY-MM-DD

Key Rules for Program Files

• Show actual values, never blanks for existing data. If an indicator existed in a year, show its value. Use "—" ONLY when the indicator genuinely didn't exist that year.
• Footnote classification changes. If an indicator moved between Outcome/Output across years, show the value where it logically belongs and footnote the original classification.
• Group output indicators by category (Facility MOOE Support, PhilHealth Accreditation, Construction, Equipment, etc.) for readability.
• Attribution notes for indicators that are structurally ambiguous in the GAAB (e.g., listed under a broader section heading rather than nested under the specific program).

Mode 3: PROFILE — Ministry Profile from BAA-13

Create a ministry profile with verbatim mandates, powers and functions from BAA-13.

Structure

# [Entity Name]

## Mandate

[Verbatim mandate text from BAA-13]

## Powers and Functions

[Verbatim ministry-level powers and functions — NOT the Minister's or Deputy Minister's
individual powers]

## Organization and Composition

[Verbatim organizational structure if present in BAA-13]

---
**Source:** BAA-13 (Bangsamoro Administrative Code), Sections [X-Y]
**Extracted:** YYYY-MM-DD

Rules

• Extract VERBATIM — do not paraphrase
• Include all sub-items (a, b, c, etc.)
• Ministry-level powers only (not Minister/Deputy Minister individual powers)
• If an entity is NOT in BAA-13 (created by a separate BAA), note which BAA created it

Scaling Strategy

For processing all 300+ programs, use parallel agents:

1. By ministry batch — dispatch agents handling 3-4 ministries each, reading all 7 GAABs
2. Each agent writes the final files — no intermediate steps needed
3. Spot-check after each batch — verify one random program's amounts against source

For the full program-budgets directory (300+ files):

1. First extract the master program list from each GAAB
2. Group programs by implementing MOA
3. Dispatch agents per MOA to create all program files for that ministry
4. Each agent reads its ministry's section from all 7 GAABs + the .ts file

References