Transport and Infrastructure
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Use When
- Use this skill when the assignment is clearly in transport, mobility, logistics, or infrastructure work.
- Load it when proposal sections need sector-specific framing, terminology, stakeholders, risks, or methodology cues.
Do Not Use When
- Another sector is the closer fit and this one adds no material value.
- The task only needs procurement-form instructions without domain context.
Required Inputs
| Artefact |
Source/provider |
Required? |
Missing-input behaviour |
| The assignment brief or ToR. |
Buyer solicitation, ToR, or approved brief |
Required |
Stop the affected claim, request or verify the input, and label the resulting gap. |
| The geography and institutional context, especially if Uganda-specific evidence is relevant. |
Buyer, verified sector source, or discovery |
Required |
Stop the affected claim, request or verify the input, and label the resulting gap. |
Workflow
- Confirm the sector fit from the brief.
- Read the sector reference file for evidence, terminology, and current signals.
- Translate the sector context into problem framing, methodology choices, stakeholder logic, and risks.
- Use the sector framing inside the relevant 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
- Prefer sector detail that improves credibility and delivery realism.
- Use reference data to sharpen the proposal story, not to overwhelm it.
Anti-Patterns
- Do not paste statistics without explaining their relevance.
- Do not use sector jargon as a substitute for a clear methodology.
- 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
| Artefact |
Consumer |
Acceptance condition |
| Sector-specific framing and methodology cues for transport and infrastructure assignments. |
Proposal lead, section writer, and evaluator-readiness reviewer |
Applied consistently, traceable to the selected source, and free of unsupported identity, framework, or sector claims. |
Evidence Produced
| Evidence |
Consumer |
Acceptance condition |
| Routing and source record |
Proposal lead and reviewer |
Selected identity, framework, sector, source, date, and material gaps are recorded. |
| Decision record |
Section writer and delivery lead |
Each material choice has rationale, owner, evidence, and a review or stop condition. |
| Conformance check |
Release reviewer |
Mandatory forms, identity rules, sector logic, and unresolved checks are explicitly assessed. |
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
| Decision |
Action |
Failure/risk avoided |
| Asset and lifecycle scope |
Define asset class, corridor or geography, demand, safeguards, operations, and maintenance responsibility. |
Capital plan without lifecycle feasibility |
| Conflicting solicitation and background guidance |
Follow the solicitation while recording the conflict for formal clarification. |
Non-responsive interpretation |
| Missing mandatory evidence |
Stop the affected claim or form, record the owner and deadline, and continue only with independent supported content. |
Fabricated evidence or silent omission |
| Submission, certification, or contractual commitment |
Obtain explicit authority and preserve approval evidence before acting. |
Unauthorised external commitment |
Worked Example
A solicitation requires asset and lifecycle scope, but one controlling input is missing. The proposal team applies this rule: Define asset class, corridor or geography, demand, safeguards, operations, and maintenance responsibility. It records the gap and owner, withholds the affected assurance, and proceeds only with content that can be verified. This avoids capital plan without lifecycle feasibility.
References
- references/uganda-transport-sector.md for local sector context.
- ../SKILL.md to combine this sector with procurement context.
1---2name: transport-infrastructure3description: Use when a proposal concerns roads, mobility, logistics, urban transport, infrastructure planning, asset management, or PPP advisory; use manufacturing-industrial for factory and warehouse operations.4---56# Transport and Infrastructure7Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.89<!-- dual-compat-start -->10## Use When11- Use this skill when the assignment is clearly in transport, mobility, logistics, or infrastructure work.12- Load it when proposal sections need sector-specific framing, terminology, stakeholders, risks, or methodology cues.1314## Do Not Use When15- Another sector is the closer fit and this one adds no material value.16- The task only needs procurement-form instructions without domain context.1718## Required Inputs1920| Artefact | Source/provider | Required? | Missing-input behaviour |21|---|---|---|---|22| The assignment brief or ToR. | Buyer solicitation, ToR, or approved brief | Required | Stop the affected claim, request or verify the input, and label the resulting gap. |23| The geography and institutional context, especially if Uganda-specific evidence is relevant. | Buyer, verified sector source, or discovery | Required | Stop the affected claim, request or verify the input, and label the resulting gap. |2425## Workflow26271. Confirm the sector fit from the brief.282. Read the sector reference file for evidence, terminology, and current signals.293. Translate the sector context into problem framing, methodology choices, stakeholder logic, and risks.304. Use the sector framing inside the relevant numbered proposal section skills.3132**Stop condition:** Stop when proposer identity, controlling framework, mandatory form, sector fit, current rule, or load-bearing evidence remains unresolved.3334**Recovery:** Record the gap and owner, seek clarification or current evidence, and return only the separable proposal content that remains supportable.3536## Quality Standards37- Prefer sector detail that improves credibility and delivery realism.38- Use reference data to sharpen the proposal story, not to overwhelm it.3940## Anti-Patterns4142- Do not paste statistics without explaining their relevance.43- Do not use sector jargon as a substitute for a clear methodology.44- Treating a neighbouring sector or framework as interchangeable. **Fix:** identify the controlling rule and primary outcome.45- Adding terminology without changing a delivery choice. **Fix:** link each term to method, risk, output, or evaluation criterion.46- Presenting an unverified current rule or statistic as settled. **Fix:** cite and date the source or mark it not assessed.47- Ignoring a missing mandatory input. **Fix:** stop the affected claim and assign an evidence owner.48- Letting sector or identity framing contradict methodology, staffing, schedule, or price. **Fix:** reconcile all affected sections before release.4950## Outputs5152| Artefact | Consumer | Acceptance condition |53|---|---|---|54| Sector-specific framing and methodology cues for transport and infrastructure assignments. | Proposal lead, section writer, and evaluator-readiness reviewer | Applied consistently, traceable to the selected source, and free of unsupported identity, framework, or sector claims. |5556## Evidence Produced5758| Evidence | Consumer | Acceptance condition |59|---|---|---|60| Routing and source record | Proposal lead and reviewer | Selected identity, framework, sector, source, date, and material gaps are recorded. |61| Decision record | Section writer and delivery lead | Each material choice has rationale, owner, evidence, and a review or stop condition. |62| Conformance check | Release reviewer | Mandatory forms, identity rules, sector logic, and unresolved checks are explicitly assessed. |6364## Capability Contract6566This 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.6768## Degraded Mode6970If 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.7172## Decision Rules7374| Decision | Action | Failure/risk avoided |75|---|---|---|76| Asset and lifecycle scope | Define asset class, corridor or geography, demand, safeguards, operations, and maintenance responsibility. | Capital plan without lifecycle feasibility |77| Conflicting solicitation and background guidance | Follow the solicitation while recording the conflict for formal clarification. | Non-responsive interpretation |78| Missing mandatory evidence | Stop the affected claim or form, record the owner and deadline, and continue only with independent supported content. | Fabricated evidence or silent omission |79| Submission, certification, or contractual commitment | Obtain explicit authority and preserve approval evidence before acting. | Unauthorised external commitment |8081## Worked Example8283A solicitation requires **asset and lifecycle scope**, but one controlling input is missing. The proposal team applies this rule: Define asset class, corridor or geography, demand, safeguards, operations, and maintenance responsibility. It records the gap and owner, withholds the affected assurance, and proceeds only with content that can be verified. This avoids **capital plan without lifecycle feasibility**.8485## References8687- [Proposal skill router](../../../SKILL.md) — orchestration, profile, reasoning, and release gates.88<!-- dual-compat-end -->89- [references/uganda-transport-sector.md](references/uganda-transport-sector.md) for local sector context.90- [../SKILL.md](../SKILL.md) to combine this sector with procurement context.
peterbamuhigire