tor-to-proposal 2.0.0

package/package.json

@@ -0,0 +1,57 @@
+{
+  "name": "tor-to-proposal",
+  "version": "2.0.0",
+  "description": "The bid tool that refuses to lie. ToR + CV in -> verified bid pack out: cover letter, tailored CV, technical response, financial proposal, submission checklist. Deterministic CLI + agent skill for UN / NGO / government consultants.",
+  "type": "module",
+  "bin": {
+    "tor-to-proposal": "bin/tor-to-proposal.mjs"
+  },
+  "files": [
+    "bin/",
+    "mcp/",
+    "commands/",
+    "assets/",
+    "references/",
+    "library/",
+    "docs/",
+    "SKILL.md",
+    "README.md",
+    "LICENSE",
+    ".claude-plugin/"
+  ],
+  "scripts": {
+    "test": "node test/run-tests.mjs",
+    "postinstall": "node -e \"console.log('tor-to-proposal installed. Run: tor-to-proposal init (one-time profile wizard).')\""
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "dependencies": {
+    "adm-zip": "^0.5.16",
+    "exceljs": "^4.4.0",
+    "mammoth": "^1.8.0",
+    "unpdf": "^1.8.1"
+  },
+  "keywords": [
+    "tor",
+    "proposal",
+    "un",
+    "ungm",
+    "undp",
+    "consultant",
+    "tender",
+    "bid",
+    "rfp",
+    "cover-letter",
+    "financial-proposal",
+    "cv",
+    "agent-skills",
+    "mcp"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/ahaomar/tor-to-proposal.git"
+  },
+  "homepage": "https://github.com/ahaomar/tor-to-proposal#readme",
+  "license": "MIT"
+}

package/references/packs/eu-prag.md

@@ -0,0 +1,29 @@
+# EU PRAG pack (EuropeAid / NEAR / INTPA service & works contracts)
+
+## Where things live
+- Solicitations: EU Funding & Tenders portal (ec.europa.eu/eurostat beyond —
+  use the Funding & Tenders portal search); EuropeAid procurement.
+- Rules: PRAG — Practical Guide for contract award (international
+  cooperation); the document is authoritative, edition-sensitive, and free
+  online. ALWAYS check the PRAG edition named in the ToR.
+
+## Structure conventions to verify
+- Service contracts: full procedure with technical offer + financial offer
+  sealed separately; shortlisting stages for restricted procedures.
+- Evaluation grids published in the ToR annexes — often the most detailed of
+  any donor (organization, methodology, key experts, proven experience).
+  Extract sub-elements verbatim into sub-elements.json for the simulator.
+- Key experts: the grid scores named experts' qualifications — a firm bid
+  lives or dies on CV-grid fit (run cv-gap per expert).
+
+## Financial side
+- Price schedule per deliverable or per expert-day; VAT rules by contract
+  type (international services often zero-rated, local services not).
+- Global pricing rules in the instructions to tenderers; budget caps stated.
+
+## Watch for
+- Eligibility rules (origin of tenderer, nationality of experts) are strict
+  and disqualifying.
+- Declaration on honour + exclusion criteria forms required at submission.
+- Clarification deadlines and a public Q&A published as an annex — check for
+  addenda before finalizing; they change grids.

package/references/packs/undp.md

@@ -0,0 +1,30 @@
+# UNDP pack
+
+Conventions to verify in the ToR — never assume; UNDP templates vary by
+country office and year.
+
+## Where things live
+- Solicitations: UNGM (ungm.org) → "UNDP" + country; some IC/SSA posts also on
+  the country-office site and jobs portals.
+- Rules: UNDP Procurement Policy (pop.undp.org) — the ToR's GCCs derive from it.
+- Vendor registration: UNGM vendor account (needed before award, not always
+  before bidding — check the ToR's eligibility section, p.X).
+
+## Typical structure of an individual-consultant (IC) solicitation
+- Two-envelope: technical first; financial opened only above the technical
+  threshold (commonly 70/30 technical/financial — VERIFY the split and the
+  threshold in the ToR's evaluation section, p.X).
+- Technical grid commonly covers education, relevant experience, methodology/
+  approach, languages. Extract the actual grid with extract.mjs; do not reuse
+  this sketch.
+
+## Financial side
+- Financial Proposal form is usually an Excel annex — template-filler `map`
+  it; totals must remain the form's own formulas.
+- IC contracts are output-based lump sums in most country offices; daily fee
+  × estimated days appears in the form; check whether travel is included.
+
+## Watch for
+- "No deviation" GCC acceptance line — echo it verbatim in the cover letter.
+- Clarification deadline is separate from submission deadline.
+- Attested copies of degrees/diplomas sometimes required WITH the offer.

package/references/packs/usaid.md

@@ -0,0 +1,29 @@
+# USAID pack
+
+## Where things live
+- Solicitations: sam.gov (US federal single portal) for direct contracts;
+  BAA/RFAs on grants.gov; much USAID consultancy flows through implementers
+  (Chemonics, DAI, FHI 360, RTI...) who subcontract with their own portals —
+  identify WHICH track the ToR belongs to first.
+- Rules: ADS 300s (acquisition/assistance policy), FAR/DFARS for contracts;
+  implementers follow their own prime-award terms.
+
+## Conventions to verify
+- Direct contracts: evaluation per FAR 15.3 or best-value tradeoff — the
+  ToR/RFQ states the significant factors and their order; mirror them.
+- Subcontracts (most common for consultants): prime's template governs;
+  NTE (not-to-exceed) rates; mark-up structures are the prime's, not yours.
+- Personal services contractors (PSC): published salary bands (GS/FS
+  equivalents) — a real, citable benchmark for market-rates-research.
+
+## Financial side
+- Rates commonly quoted all-inclusive daily; travel billed separately at
+  actuals with caps (Fly America for US-origin travel).
+- Payment terms of the prime flow down — verify payment reputation
+  (dossier) before quoting tight contingency.
+
+## Watch for
+- US nationality/citizenship requirements for some PSCs.
+- Organizational conflict-of-interest certifications.
+- OFAC sanctions screening clauses — relevant if you work in sanctioned
+  adjacent environments.

package/references/packs/worldbank.md

@@ -0,0 +1,26 @@
+# World Bank / IFI pack
+
+## Where things live
+- Solicitations: World Bank eProcurement / vendor portal (worldbank.org);
+  consultant opportunities under STC (Short-Term Consultant) and firm CQS/RFQ
+  tracks.
+- Rules: Procurement Regulations and Consultant Guidance (pubdocs.worldbank.org).
+- Vendor registration: World Bank Supplier Portal (needed for contracting).
+
+## STC (individual consultant) conventions
+- Daily rate + business travel expenses quoted separately; STC maximum daily
+  rate schedule exists — the effective ceiling changes by fiscal year: verify
+  the current schedule and cite it (source + date) in market-rates-research.
+- Evaluation: CV against stated criteria; sometimes a short technical
+  response. Extract the actual criteria; never assume the common
+  education/experience/language sketch.
+
+## Firm consultations (CQS/RFQ/RFP)
+- Budget caps are often pre-announced — price discovery is partly given;
+  position still matters for the technical/financial mix in RFPs.
+
+## Watch for
+- COI disclosure requirements (relatives at the Bank, prior Bank employment).
+- "Not to exceed X days" ceilings: pricing beyond them is at your risk.
+- Deliverable-based STCs: milestone table drives payment; mirror it in the
+  technical response.

package/references/pricing-standards.md

@@ -0,0 +1,52 @@
+# Pricing standards — read before step 5 (pricing-model)
+
+## Conventions used by the tool (open constants)
+
+- 8 hours/day, 5 days/week, 4.33 weeks/month (173.3 h/month).
+- Formats interconvert from one base rate; every line prints its formula so a
+  reviewer can reproduce it with a calculator.
+
+## Loading (overhead multiplier)
+
+Loading covers what the ToR does not pay for: insurance, professional
+software, unpaid proposal time, leave without pay, pension. Common practice
+for independent consultants on lump-sum UN/IFI work: 20–35%. Below 20%
+usually means the consultant is subsidizing the client; above 40% needs a
+written justification in your own records. These are conventions to sanity
+check your own number — the number itself is the user's.
+
+## Contingency
+
+Contingency prices the risks you can document: payment delay reputation of the
+client (from the dossier), currency/FX exposure, scope-creep-prone
+deliverables, extended review cycles. 5–15% is the common band. Zero
+contingency is a choice, not a virtue — make it consciously.
+
+## Floor (decision rule — printed by every rate tool)
+
+```
+floor = (minimum acceptable net income for the period
+         ÷ realistic billable days in that period) + overhead
+```
+
+A quote below floor is a subsidy to the client; a quote above your cited
+benchmark band needs a premium justification (scarce expertise, faster
+delivery, lower client risk).
+
+## Cost-reimbursable vs lump-sum
+
+- Cost-reimbursable: time actually worked is invoiced; loading shows as a rate.
+- Lump-sum: you carry delivery risk; loading + contingency belong INSIDE the
+  figure — which is also what most client financial forms require (a single
+  daily fee or fixed deliverable prices, no visible loading lines).
+
+## Client form discipline
+
+- The client's financial form governs. Restructure into it (template-filler),
+  never restructure it into your model.
+- If the form forbids loading lines: present the loaded figure only, and keep
+  the decomposition in your own pricing.json for your records.
+- Per-team-member breakdowns: each person's rate must individually trace to
+  their floor or a cited benchmark.
+- Some forms include honorarium/DSA/transport fields — leave them [FILL]
+  unless the ToR states amounts; never guess per-diems.

package/references/render-specs.md

@@ -0,0 +1,60 @@
+# Render specs — the four final documents
+
+You render these with your own document tooling (PDF preferred, docx
+acceptable). `package.mjs` then re-extracts the text of whatever you produce
+and re-runs the audit — so quality here is verified, not assumed. If you have
+no document tooling, `bid-pack pack --fallback-pdf` produces plain but valid
+PDFs with the built-in renderer.
+
+Shared rules for all four documents:
+
+- A4, margins ≥ 2 cm, single column, no headers/footers that obscure text.
+- Fonts: one serif or sans family; name/credentials exactly as in the profile.
+- File names are fixed — `package.mjs` looks for exactly these:
+  `cover-letter.pdf`, `cv-tailored.pdf`, `technical-proposal.pdf`,
+  `financial-proposal.pdf` (or `.xlsx` for the financial pack).
+- Page numbers bottom-center on documents longer than one page.
+- No placeholders survive: `[FILL]`, `{{...}}`, lorem, or "TODO" anywhere in
+  the rendered bytes is a hard fail.
+- Keep citations readable: "(p.X)" stays inline in the text. `[[PAGE n]]` tags
+  are for internal tools and must NOT appear in rendered output.
+
+## Cover letter — Cover-Letter.pdf
+
+- Exactly one page. Structure per `assets/templates.md`:
+  reference block → understanding (2 sentences, cited) → fit (one block per
+  core competency, requirement quoted + evidence) → compliance declarations →
+  availability → sign-off matching the CV name + credentials.
+- 11–12 pt body, 1.15 line spacing, date top-right or under the reference
+  block, recipient block top-left.
+- No letterhead invention: if the user has no letterhead, plain and clean wins.
+
+## CV — CV.pdf
+
+- 2–4 pages. Start with identity (name + credentials, contact), then
+  "Most relevant for this assignment" (the tailor's summary block), then the
+  full reordered CV, education, languages.
+- Every line traces to the master CV or a user evidence answer — the lint
+  already proved this for the markdown; your rendering must not add anything.
+- Never include a photo, marital status, or nationality unless the ToR or the
+  user requires it (many UN forms do; follow the ToR, cite the page).
+
+## Technical response — Technical-Proposal.pdf
+
+- One section per scored criterion, highest weight first, section numbers and
+  titles verbatim from the ToR grid with weight noted ("(p.X, 30 pts)").
+- 10–12 pt body. Tables for work plans / deliverable mapping are welcome —
+  they survive re-extraction as text (verify with the pack report).
+- Length follows the ToR: if it caps pages, obey the cap and say so in the
+  compliance matrix.
+
+## Financial proposal — Financial-Proposal.pdf / .xlsx
+
+- Render from `out/financial-proposal.md` (or fill the client's own form with
+  `template-filler` — then the client's form IS the deliverable).
+- The client sees the quote: quantities, all-inclusive unit rates, amounts,
+  total, payment schedule, validity, taxes. The floor math (base, loading,
+  contingency decomposition) NEVER appears in any client-facing file —
+  `pricing.md`/`pricing.json` stay private and are not part of the pack.
+- Money format: thousands separators, 2 decimals, currency stated in the
+  header and in every column heading.

package/references/review-rules.md

@@ -0,0 +1,38 @@
+# Review rules — read before showing the user any draft
+
+## The four questions every paragraph must survive
+
+1. **Trace**: does every fact here trace to the ToR (p.X), a user input, or a cited source?
+2. **Claim**: did we claim anything the CV does not support? (GAP list is the arbiter.)
+3. **Client words**: does this paragraph use the client's own terminology, not our synonyms?
+4. **Score**: which evaluation criterion does this paragraph earn points under? If none, it is decoration — cut it.
+
+## Banned superlatives (cover-letter lint enforces this list)
+
+leading, world-class, world leading, renowned, premier, cutting-edge,
+state-of-the-art, best-in-class, unparalleled, top-tier, preeminent,
+unrivaled, foremost, exceptional expertise, vast experience.
+
+Replace each with evidence: "led 4 country evaluations (p.X requirement; CV §3)".
+
+## Style
+
+- One page cover letter, always.
+- Mirror the ToR's section names for the technical response — evaluators score
+  against a grid that follows the ToR's own structure.
+- Quantify every experience bullet. No number available → [FILL] + ask the user.
+- Passive-aggressive hedging ("we hope to potentially...") reads as weakness.
+  State facts; cite them; stop.
+- Dates, names, reference numbers: copy-paste from the ToR, never retype.
+
+## Pre-submission checklist (audit.mjs covers 1–3 mechanically)
+
+1. [ ] Zero `[FILL]` remaining.
+2. [ ] Compliance matrix: every row Complete.
+3. [ ] No claim-shaped sentence without a trace.
+4. [ ] Cover letter lint PASS.
+5. [ ] Simulator at-risk ≈ 0 (or user accepted the residual consciously).
+6. [ ] Financial form totals are the CLIENT's formulas (we never overwrite them).
+7. [ ] File names per submission instructions (some portals reject wrong names).
+8. [ ] Submitted via the ToR's channel only, before the deadline, in the
+       timezone the ToR states ("17:00 GMT" is not your local 17:00).