---
name: rfp
description: Guided entry point for the full RFP response pipeline — from arrival through qualification, shredding, compliance matrix, section drafting, case study selection, and executive summary in one coherent flow.
---

# /rfp — RFP Response Assistant

This command is the guided entry point for the full RFP response pipeline.

## Usage

```
/rfp                               # Interactive mode — guided prompts
/rfp qualify <rfp-file>            # Run score-rfp-fit on the opportunity
/rfp shred <rfp-file>              # Run rfp-shred — extract requirements register
/rfp matrix <register-file>        # Run build-compliance-matrix from the register
/rfp cases <register-file>         # Run select-case-studies for the opportunity
/rfp draft <section> <register>    # Run draft-rfp-section for a specific section
/rfp summary <response-dir>        # Run draft-executive-summary from all drafted sections
/rfp review <response-dir>         # Run rfp-reviewer for final compliance check
/rfp full <rfp-file>               # Run the full pipeline end-to-end
```

## Interactive mode (default)

When run without arguments, prompt the user:

```
Welcome to the RBA RFP Response Assistant.

What would you like to do?

1. Qualify this opportunity (go/no-go scorecard)
2. Shred the RFP — extract requirements and build a register
3. Build the compliance matrix and assign owners
4. Select the best case studies for this bid
5. Draft a specific response section
6. Draft the executive summary
7. Run the final review before submission
8. Run the full pipeline end-to-end

Enter a number or describe what you need:
```

Based on the response, invoke the appropriate skill:

| Choice | Skill/agent invoked |
|---|---|
| 1 | `score-rfp-fit` |
| 2 | `rfp-shred` |
| 3 | `build-compliance-matrix` |
| 4 | `select-case-studies` |
| 5 | `draft-rfp-section` (prompt for section name) |
| 6 | `draft-executive-summary` |
| 7 | `rfp-reviewer` agent |
| 8 | Full pipeline in sequence |

## Full pipeline mode (option 8 or `/rfp full`)

Run the skills in sequence with handoffs:

1. **Qualify** — Run `score-rfp-fit` on the RFP.
   - Ask: "Score is [N/5] — recommendation: [Go/No-Bid]. Proceed with full response? (yes / no)"
   - If no-bid: stop and provide the decline communication from the scorecard.

2. **Shred** — Run `rfp-shred` on the RFP.
   - Output: `rfp-register-[client-slug]-[date].md`
   - Ask: "Register complete. [N] requirements extracted. Proceed to compliance matrix? (yes / review register first)"

3. **Matrix** — Run `build-compliance-matrix` on the register.
   - Output: `compliance-matrix-[client-slug]-[date].md`
   - Ask: "Matrix built. [N] Red risks, [N] Amber risks. Assign owners and proceed to drafting? (yes / review matrix first)"

4. **Cases** — Run `select-case-studies` on the register.
   - Output: case study selection report (terminal)
   - Ask: "Case studies selected. Save this report to a file? (yes / proceed to drafting)"

5. **Draft sections** — For each section in the compliance matrix (ordered by weight, highest first):
   - Run `draft-rfp-section` for the section
   - Output: `response-[section-slug]-[client-slug]-[date].md`
   - Ask: "Section drafted. Continue to next section? (yes / review this section first)"

6. **Executive summary** — Run `draft-executive-summary` on all drafted section files.
   - Output: `executive-summary-[client-slug]-[date].md`
   - Ask: "Executive summary drafted. Proceed to final review? (yes / review summary first)"

7. **Review** — Run `rfp-reviewer` agent on all response files.
   - Output: review report (terminal)
   - If BLOCKERs found: list them and ask "Address BLOCKERs before submission? (yes — fix now / no — I'll fix manually)"

## File naming convention

All output files follow the pattern: `[artifact]-[client-slug]-[YYYY-MM-DD].md`

Examples:
- `rfp-register-acme-bank-2026-06-01.md`
- `compliance-matrix-acme-bank-2026-06-01.md`
- `response-technical-approach-acme-bank-2026-06-01.md`
- `executive-summary-acme-bank-2026-06-01.md`

If no client slug can be inferred, use `new-opportunity`.

## Answer library setup

The pipeline reads from `rfp-library/` in the current directory. On first use, run:

```
/rfp          # then choose option 2 (shred) to generate the register
```

If `rfp-library/` does not exist, the skills will flag `[CONTENT NEEDED]` placeholders and continue — they degrade gracefully, never hallucinate.

To bootstrap the library, create the directory structure and populate with RBA content:

```
rfp-library/
  capabilities/
  case-studies/
  security-posture/
  certifications/
  team-bios/
  boilerplate/
```

## Tips

- Run `/rfp qualify` first, every time. Unqualified bids waste everyone's time.
- Share the compliance matrix at kick-off — every team member needs the same view of requirements.
- The answer library is the multiplier: the richer it is, the faster and better every subsequent bid.
- The `rfp-reviewer` agent is the final gate. Treat its BLOCKERs as mandatory before submission.
- When in doubt about platform: use `--platform agnostic` and let the requirements register guide which adapter to apply.