acquisition-policy-workflowlisted

Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing prior policy analysis; or producing an Acquisition Policy Impact Brief. Use published federal sources and supplied policy documents without making legal or procurement-specific applicability determinations. Do not use for clause selection, market research execution, opportunities, pricing, grants, or cooperative agreements.
1102tools-dev/federal-contracting-agents · ★ 3 · AI & Automation · score 76

Install: claude install-skill 1102tools-dev/federal-contracting-agents

# Acquisition Policy Workflow ## Purpose Explain and trace published federal acquisition policy with an explicit as-of date, source hierarchy, and documented-status boundary. Support concise sourced chat answers and a validated Acquisition Policy Impact Brief `.docx` for government, industry, or neutral audiences. The complete workflow uses the eCFR, Federal Register, Regulations.gov, and Acquisition.gov MCP servers. Use only the capabilities required by the selected mode. Do not substitute direct HTTP, shell requests, or a general web provider for a missing required MCP. Read supporting files only when their stage is reached: - [launch-menu-and-framing.md](references/launch-menu-and-framing.md) for mode routing and exact framing questions. - [document-intake.md](references/document-intake.md) when the user supplies policy files, paths, or pasted text. - [source-routing.md](references/source-routing.md) before planning or retrieving evidence. - [status-and-decision-boundaries.md](references/status-and-decision-boundaries.md) before classifying policy status or presenting findings. - [evidence-contract.md](references/evidence-contract.md) whenever creating or updating the policy-research record. - [report-specification.md](references/report-specification.md) before generating a brief. - [runtime-adaptation.md](references/runtime-adaptation.md) when capabilities, files, or document tooling differ by host. ## Permanent gates 1. **Route before retrieval:** A vague request