/public-records-plan
Research, draft, and track a jurisdiction-specific public-records request without legal conclusions or automated submission.
Claude Code
$ npx -y skills add jmagly/aiwg --skill public-records-plan --agent claude-code
Codex
$ npx skills add jmagly/aiwg --skill public-records-plan -a codex -y
Cursor
$ npx skills add jmagly/aiwg --skill public-records-plan -a cursor -y
Gemini CLI
$ npx skills add jmagly/aiwg --skill public-records-plan -a gemini-cli -y
GitHub Copilot
$ npx skills add jmagly/aiwg --skill public-records-plan -a github-copilot -y
OpenCode
$ npx skills add jmagly/aiwg --skill public-records-plan -a opencode -y
Windsurf
$ npx skills add jmagly/aiwg --skill public-records-plan -a windsurf -y
SKILL.md
public-records-plan.SKILL.mdnamespace: aiwg
platforms: [all]
name: public-records-plan
description: Research, draft, and track a jurisdiction-specific public-records request without legal conclusions or automated submission.
triggers:
- plan a public records request
- draft a FOIA request for human review
- track a records request and response
Public Records Plan
Process
1. Check already-published sources, then resolve a current official jurisdiction and agency profile. Never fall back from state/local law to federal FOIA. 2. Describe records, custodians, systems, dates, formats, exclusions, fee ceiling, urgency, privacy minimization, and source-linked contact details. 3. Mark calculated dates as estimates derived from an approved profile; preserve agency-provided dates separately. 4. Produce a versioned draft marked `NOT REVIEWED — DO NOT SEND` until a named human approves the exact version. Submission is always manual. 5. Hash and quarantine responses; preserve originals and label OCR/extraction as derived. Do not reverse redactions or construct personal dossiers. 6. Track sent and observed/calculated due dates separately, status/fees, response artifact hashes, revision and appeal windows, and the linked investigation. Support PDF, scan, email, spreadsheet, and attachment inputs.
Output
A `public-records-plan` artifact, evidence checklist, and pending human action.
References
- `templates/public-records-plan.md`
- `schemas/public-records-plan.schema.json`
- `docs/research/legal-ethics-guardrails.md`
- `docs/research/control-source-matrix.md`
Read more
namespace: aiwg platforms: [all] name: public-records-plan description: Research, draft, and track a jurisdiction-specific public-records request without legal conclusions or automated submission. triggers: - plan a public records request - draft a FOIA request for human review - track a records request and response
Public Records Plan
Process
1. Check already-published sources, then resolve a current official jurisdiction and agency profile. Never fall back from state/local law to federal FOIA. 2. Describe records, custodians, systems, dates, formats, exclusions, fee ceiling, urgency, privacy minimization, and source-linked contact details. 3. Mark calculated dates as estimates derived from an approved profile; preserve agency-provided dates separately. 4. Produce a versioned draft marked `NOT REVIEWED — DO NOT SEND` until a named human approves the exact version. Submission is always manual. 5. Hash and quarantine responses; preserve originals and label OCR/extraction as derived. Do not reverse redactions or construct personal dossiers. 6. Track sent and observed/calculated due dates separately, status/fees, response artifact hashes, revision and appeal windows, and the linked investigation. Support PDF, scan, email, spreadsheet, and attachment inputs.
Output
A `public-records-plan` artifact, evidence checklist, and pending human action.
References
- `templates/public-records-plan.md`
- `schemas/public-records-plan.schema.json`
- `docs/research/legal-ethics-guardrails.md`
- `docs/research/control-source-matrix.md`
Reusable project context and specialist workflows for the AI tools you already use. Plan software, coordinate specialist reviews, prepare campaigns, investigate incidents, organize research, curate media, and maintain operational knowledge.
Other skills on aiwg.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about public-records-plan.
- Which coding agents can use public-records-plan?
- public-records-plan installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

