aiskillstore/marketplace / skills/1102tools-dev/acquisition-policy-workflow
acquisition-policy-workflow
VerifiedTrigger 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.5 KB |
| agents/openai.yaml | config | 281 B |
| references/document-intake.md | markdown | 1.5 KB |
| references/evidence-contract.md | markdown | 3.8 KB |
| references/launch-menu-and-framing.md | markdown | 3.1 KB |
| references/report-specification.md | markdown | 2.1 KB |
| references/runtime-adaptation.md | markdown | 1.4 KB |
| references/source-routing.md | markdown | 3.8 KB |
| references/status-and-decision-boundaries.md | markdown | 3.9 KB |
| scripts/build_acquisition_policy_brief.py | script | 20.4 KB |
| scripts/validate_acquisition_policy_brief.py | script | 7.3 KB |
| scripts/validate_policy_research_record.py | script | 23.6 KB |
| skill-report.json | config | 41.7 KB |
| test.md | markdown | 1.6 KB |
| testing.md | markdown | 2.2 KB |
references/report-specification.md
View on GitHub# Acquisition Policy Impact Brief specification
## Required sections
1. Executive Summary
2. Question and Scope
3. Documented Current Status
4. Source Hierarchy and Authorities
5. Change Timeline
6. Government and Industry Impacts
7. Open Issues and Comment Deadlines
8. Operational Considerations
9. Evidence Register
10. Limitations and Reserved Determinations
Use the `standard_business_brief` visual preset with a restrained memo masthead. Use US Letter portrait, one-inch margins, Calibri 11-point body text, blue heading hierarchy, quiet running header/footer, real list styles, and fixed-width tables with repeating header rows.
The title block states the agency or scope, as-of date, audience lens, and preparation status. Do not call the brief a legal opinion, authoritative policy determination, or contract-file approval.
## Evidence presentation
- Put evidence IDs beside every consequential finding and impact statement.
- Preserve canonical public hyperlinks in the evidence register.
- Keep codified text, agency deviations, model text, rulemaking, guidance, and public comments visually distinguishable.
- Use tables only for repeated comparable records such as policy layers, timelines, and the evidence register.
- Do not place internal prompts, tool names, filesystem paths, credentials, or raw private text in the document.
## Impacts
Government and industry lenses use the same evidence. They may differ only in operational framing:
- Government: acquisition planning, solicitation timing, internal policy confirmation, transition treatment, and file documentation.
- Industry: solicitation interpretation questions, proposal assumptions, compliance planning, timing, and monitoring.
- Neutral: both lenses without advocacy.
Impacts are considerations, not directives or legal conclusions.
## Validation
The builder requires `validation.findings_approved` and `validation.brief_approved` to be true. The validator checks section order, evidence-ID coverage, live hyperlinks, as-of date, decision-boundary language, fixed table geometry, repeating headers, prohibited internal content, and policy-record validity.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |