developing-teaming-strategylisted

# Developing Teaming Strategy Build the team. Most federal pursuits cannot be won by the prime alone — there are capability gaps, past-performance gaps, socioeconomic requirements, or scope that a partner does better. Teaming is the workstream that turns "we need help" into a defined team with defined workshare, signed agreements, and the data the proposal needs. Done late or loosely, teaming becomes the thing that constrains the bid; done deliberately, it is a source of strength. ## When to use this skill Use this skill during the capture phase, once the opportunity is being pursued and the requirement is understood well enough to see where the prime needs help. Re-run it as the requirement firms up through the draft RFP and RFP. It is related to but distinct from `planning-capture` (which tracks teaming *actions* at a summary level) and `developing-solution-approach` (which designs *what* the team does). This skill decides *who* is on the team and *on what terms*. ## Inputs **Preferred upstream artifacts:** - `00-opportunity-profile.md`: scope, contract type, set-aside, vehicle. - `02-capture-plan.md`: the capability and past-performance gaps already noted. - `01-bid-decision.md`: gaps the bid/no-bid identified, including any that were conditional-bid conditions. - `03-competitive-assessment.md`: what the team must be strong enough to beat. Read `../../shared/glossary.md` and `../../shared/pursuit-workspace.md` if not already read this session. ## Intake Ask thes