Sectors

Sectors — Index

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use When

• Use this skill when a proposal needs both procurement-framework guidance and sector-domain context.
• Load it when you must decide which procurement and sector skills to read before drafting.

Do Not Use When

• The task is only language editing or proposer-profile selection.
• A specific sector and framework skill have already been chosen and no routing help is needed.

Required Inputs

Workflow

1. Identify the procurement framework first because it controls forms, scoring, and compliance rules.
2. Identify the industry sector next because it shapes terminology, methodology, and evaluator expectations.
3. Load one procurement skill and one or more sector skills as needed for the assignment.
4. Read country context where it materially improves the proposal.
5. Carry those assumptions into the numbered proposal section skills.

Stop condition: Stop when proposer identity, controlling framework, mandatory form, sector fit, current rule, or load-bearing evidence remains unresolved.

Recovery: Record the gap and owner, seek clarification or current evidence, and return only the separable proposal content that remains supportable.

Quality Standards

• Use procurement skills for compliance logic and sector skills for domain logic.
• Prefer the smallest relevant set of context files so the proposal stays focused.
• Treat sector references as evidence and framing support, not text to paste verbatim.

Anti-Patterns

• Do not assume the donor framework from sector keywords alone.
• Do not load every sector reference when only one or two are relevant.
• Do not ignore country context when the bid is explicitly country-specific.
• Treating a neighbouring sector or framework as interchangeable. Fix: identify the controlling rule and primary outcome.
• Adding terminology without changing a delivery choice. Fix: link each term to method, risk, output, or evaluation criterion.
• Presenting an unverified current rule or statistic as settled. Fix: cite and date the source or mark it not assessed.
• Ignoring a missing mandatory input. Fix: stop the affected claim and assign an evidence owner.
• Letting sector or identity framing contradict methodology, staffing, schedule, or price. Fix: reconcile all affected sections before release.

Outputs

Evidence Produced

Capability Contract

This skill may read supplied profiles, solicitations, ToRs, approved references, and proposal drafts and may prepare routing guidance or draft content within the authorised workspace. Review is read-only by default. It must not invent credentials, certify compliance, submit a bid, accept terms, publish, disclose confidential information, or change source records without explicit authority.

Degraded Mode

If the solicitation, profile, current procurement source, sector evidence, network, or reviewer is unavailable, provide the narrowest useful qualified routing or draft. Mark the missing check not assessed, omit unsupported credentials, thresholds, dates, or compliance claims, and identify the evidence owner. An unassessed requirement is never a pass.

Decision Rules

Worked Example

A solicitation requires controlling framework, but one controlling input is missing. The proposal team applies this rule: Use the solicitation's stated rules; pair one procurement framework with every materially relevant industry sector. It records the gap and owner, withholds the affected assurance, and proceeds only with content that can be verified. This avoids wrong forms, thresholds, terminology, or evaluation strategy.

References

• Proposal skill router — orchestration, profile, reasoning, and release gates.

• Local framework and sector subdirectories.
• uganda-country-profile.md when Uganda context matters.

This directory contains reference documentation for procurement frameworks and industry sectors. Each file defines the specifics that apply when writing proposals for that context — mandatory forms, evaluation weightings, compliance requirements, terminology, and sector-specific content expectations.

How to Use

1. Identify the procurement framework (how the bid must be structured)
2. Identify the industry sector (what the bid is about)
3. Read both files before drafting any proposal section
4. A single proposal may reference one framework + one or more sectors

Procurement Frameworks

These define how bids must be packaged, what forms are required, and how they are evaluated.

Country Profile

Industry Sectors

These define what evaluators expect in terms of domain knowledge, terminology, methodology, and deliverables for bids in each sector. Each sector now includes Uganda-specific reference data from the AfDB Country Diagnostic Note (December 2025) and the UN Uganda SDG Analysis Report Summary (2025), including SDG pathway alignment.

File Structure

Each sector or framework directory contains:

sectors/
├── INDEX.md                          ← this file
├── ppda-uganda/
│   ├── README.md                     ← overview and compliance checklist
│   ├── evaluation-criteria.md        ← scoring weights, mandatory requirements
│   ├── forms-and-templates.md        ← required submission forms
│   └── terminology.md                ← PPDA-specific terms and definitions
├── agriculture/
│   ├── README.md                     ← sector overview
│   ├── methodology-notes.md          ← common frameworks and approaches
│   ├── terminology.md                ← sector-specific vocabulary
│   └── sample-deliverables.md        ← typical deliverables and formats
└── ...

Not every directory needs every file from day one. Start with a README.md and add reference files as the sector knowledge builds.

Adding a New Sector or Framework

1. Create a subdirectory under sectors/
2. Add a README.md with an overview, key requirements, and a compliance checklist
3. Add reference files as needed (terminology, evaluation criteria, methodology notes)
4. Update this INDEX.md with the new entry