managing-proposal-operationslisted

# Managing Proposal Operations Run the proposal as a project. The other proposal skills produce artifacts — a compliance matrix, an outline, drafted sections. This skill produces the *operating system* that gets those artifacts written, reviewed, corrected, and submitted on time by the right people. In real proposal shops this is where bids are won or lost operationally: a strong solution that misses the schedule, skips a review, or fumbles an amendment still loses. ## When to use this skill Use this skill at proposal kickoff — when the RFP releases (or a draft RFP makes kickoff worthwhile) — and throughout the proposal phase to keep the effort on track. It is the hub skill for proposal development: it coordinates the work that `shredding-solicitations`, `outlining-proposals`, the drafting skills, the review skills, and `checking-submission-compliance` perform. It does not produce proposal content. It produces the plan, schedule, assignments, action register, question log, and review logistics that the content skills run inside. ## Inputs **Required:** the solicitation, including Section L (volumes, format, due date) and any submission instructions. **Preferred upstream artifacts:** - `10-compliance-matrix.md`: the requirement inventory the volume plan and assignments are built around. - `00-opportunity-profile.md`, `05-win-strategy.md` — orienting context. Read `../../shared/glossary.md`, `../../shared/proposal-lifecycle.md`, and `../../shared/pursuit-workspace.md`