Agent skill · aiskillstore
acquisition-policy-workflow
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.
What it needs
About 7k tokens when loaded.
What this skill does
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 for mode routing and exact framing questions. document-intake.md when the user supplies policy files, paths, or pasted text. source-routing.md before planning or retrieving evidence. status-and-decision-boundaries.md before classifying policy status or presenting findings. evidence-contract.md whenever creating or updating the policy-research record. report-specification.md before generating a brief. runtime-adaptation.md when capabilities, files, or document tooling differ by host. Permanent gates 1. Route before retrieval: A vague request or an invocation without a defined task receives the complete menu and selection question. An unambiguous request enters its matching mode directly. Treat a user's explicit policy-status assertion or instruction as a defined boundary-check request even when phrased as a command; correct an unsupported current-status claim directly instead of showing the menu. 2. Required framing: Establish the question, as-of date, and necessary identifiers before retrieval. Agency-specific status also requires the agency and relevant FAR part or citation. Ask for government, industry, or neutral lens only when impact depends on audience. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/acquisition-policy-workflow