BdM-15/capture-insights / skills/proposal-generator
proposal-generator
VerifiedShipley-methodology federal proposal outline and section drafter. USE WHEN the user asks to draft a proposal volume, build an outline from the proposal_instruction ↔ evaluation_factor traceability (UCF Section L/M or equivalent for non-UCF — FAR 16 task orders, FOPRs, BPA calls, OTAs, agency-specific formats), generate a compliance matrix, write win themes, draft an executive summary, propose FAB (Feature → Advantage → Benefit) chains, identify discriminators, or 'respond to this RFP'. Pulls requirements, evaluation factors, instructions, customer priorities, and pain points from the active Theseus workspace KG and produces an evidence-cited draft. Also ships govcon HTML render templates under assets/ — hand the rendered content off to the `huashu-design` skill for PPTX / PDF / animation export. Format-agnostic — never assumes UCF section labels are present. DO NOT USE FOR clause compliance auditing only (use compliance-auditor) or extracting new entities (use govcon-ontology + the Theseus pipeline).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.7 KB |
| assets/compliance_matrix.html | other | 2.7 KB |
| assets/compliance_matrix.md | markdown | 1.9 KB |
| assets/executive_summary.md | markdown | 1.1 KB |
| assets/fab_chain.md | markdown | 492 B |
| assets/one_pager.html | other | 1.5 KB |
| assets/slide_master.html | other | 1.9 KB |
| assets/theme_card.html | other | 1.3 KB |
| assets/theme_card.md | markdown | 850 B |
| assets/volume_outline.md | markdown | 653 B |
| evals/evals.json | config | 4.4 KB |
| references/anti_slop_checklist.md | markdown | 1.4 KB |
| references/critique_prompt.md | markdown | 797 B |
| references/govcon_design_tokens.md | markdown | 2.8 KB |
| references/page_budget_heuristics.md | markdown | 798 B |
| references/section_lm_traceability.md | markdown | 753 B |
| references/section_lm_visualization.md | markdown | 1.4 KB |
| references/shipley_glossary.md | markdown | 2.6 KB |
| references/win_theme_patterns.md | markdown | 1.1 KB |
assets/compliance_matrix.md
View on GitHub# Compliance Matrix Template
**Format-agnostic.** Works on UCF (Section L/M/C) and non-UCF (FAR 16 task order, FOPR, BPA call, OTA, commercial item buy, agency-specific format) alike. Column headers name the entity type first; the parenthetical shows the typical UCF mapping for reader recognition.
| # | Proposal Instruction (Section L / equiv) | Evaluation Factor (Section M / equiv) | Requirement(s) (Section C / SOW / PWS) | Volume / Section | Page Limit | Owner | Status | Evidence |
| --- | ---------------------------------------- | ------------------------------------- | -------------------------------------- | ---------------- | ---------- | -------- | ------------------ | ------------------ |
| 1 | `<instruction_id>: <verbatim text>` | `<evaluation_id>: <factor name>` | `<requirement_id list>` | `<Volume #, §>` | `<n>` | `<name>` | OK / GAP / PARTIAL | `<entity_id refs>` |
Each row also carries hidden source enums consumed by downstream renderers:
- `instruction_source`: `UCF-L | non-UCF | PWS-inline | attachment`
- `evaluation_source`: `UCF-M | non-UCF | adjectival | LPTA`
**Rules:**
1. Every row must reference at least one entity from the workspace (`proposal_instruction`, `evaluation_factor`, or `requirement`). No bare narrative rows.
2. `GAP` rows are kept in place — never deleted — and listed in the output `warnings`.
3. Status legend:
- `OK` — full instruction ↔ evaluation ↔ requirement trace + volume assignment
- `PARTIAL` — trace exists but page limit or owner missing
- `GAP` — at least one of instruction / evaluation / requirement cannot be linked to a workspace entity. **Never emit `GAP` merely because the entity lacks a literal "Section L" or "Section M" label.**
4. Sort by `proposal_instruction` order in source document, then `evaluation_factor` weight (heaviest first within a tie).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |