# Proposal voice

A reusable skill the "Draft the RFP from your past answers" recipe pulls in. Add it once and every agent on the team can use it.

Match the team's established tone and formatting standard across every drafted section.

## Method
1. Read the standard response outline and formatting rules stored in memory.
2. Match sentence length, formality, and terminology to the team's past submitted RFPs.
3. Use the product's approved feature and plan names — never an internal codename.
4. Keep section headers and numbering in the format the RFP itself requests.
5. Run a final pass across the full draft to smooth tone gaps between reused and new sections.

## Rules
- Match the RFP's required structure exactly — section order, numbering, page limits.
- Use only approved product and company terminology, never internal shorthand.
- Keep reused and newly drafted sections indistinguishable in tone after the final pass.
- Log any team style correction as a lasting formatting rule in memory, not a one-off fix.

## Output
A fully formatted draft in the RFP's required structure, saved to documents/rfps/{{account}}-{{date}}.md.
