skills/workflows/encode-policy-v2-skill/SKILL.md
Use when the user invokes $encode-policy-v2 or asks Codex to implement a new PolicyEngine-US state benefit program from official rules. Covers research, source collection, requirement extraction, scoped implementation, tests, validation, and draft PR preparation.
npx skillsauth add policyengine/policyengine-claude encode-policy-v2Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is the Codex equivalent of the Claude /encode-policy-v2 command.
Treat the text after $encode-policy-v2 as the command arguments:
$encode-policy-v2 STATE PROGRAM [--skip-review] [--research-only] [--600dpi]
Before starting, read workflow.md and subagents.md. Follow them as the source of truth for phases, checkpoints, handoff files, validation gates, and Codex subagent delegation.
Operational rules:
/tmp/{PREFIX}-... handoff files to keep large research, diffs, PDFs, and reports out of the main context.$policyengine-us, $policyengine-parameter-patterns, $policyengine-variable-patterns, $policyengine-testing-patterns, $policyengine-code-style, $policyengine-code-organization, and $policyengine-vectorization.worker or explorer agents using subagents.md; otherwise execute the same steps directly while preserving handoff-file boundaries.#page=XX, using the PDF file page number.development
ALWAYS LOAD THIS SKILL for PolicyEngine PR reviews, including when the user invokes $review-program or Codex /review on a PolicyEngine PR. Performs read-only code validation, source-reference checks, regulatory review, optional PDF audit, summary reporting, and optional GitHub comment posting.
development
Use when the user invokes $fix-pr or asks Codex to apply fixes to a PolicyEngine PR based on $review-program findings, GitHub review comments, CI failures, or local review reports.
development
Deploying PolicyEngine frontend apps to Vercel - naming, scope, team settings
development
ALWAYS LOAD THIS SKILL before writing any policyengine.py microsimulation code. Contains correct import paths, environment setup, dataset loading, and analysis patterns. Triggers: "write a script", "policyengine.py", "microsimulation script", "run a simulation", "load the dataset", "FRS", "EFRS", "enhanced FRS", "CPS", "enhanced CPS", "by income decile", "by tenure", "by region", "energy spending", "domestic energy", "household net income", "output_dataset", "ensure_datasets", "uk_datasets", "us_datasets", "import datasets", "from policyengine", "Simulation(dataset=", "uk_latest", "us_latest", "plotly", "analysis script", "decile breakdown", "percentile", "groupby", "weighted", "mean", "median", "p25", "p75", "tenure type", "income band", "policy reform script".