US State Privacy Law Assessment
Assess US state privacy law compliance for "$ARGUMENTS". Map applicable state laws, compare requirements, and create a cross-state compliance matrix.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-us-state-privacy","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-us-state-privacy","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-us-state-privacy","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run
/compliance-regulatory-landscape <project>first, or use--skip-checksto bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.mdfor GRC methodology reference - Read
references/assessment-template.mdfor output structure - Read
.singularskills/compliance/<project>/00-scope.mdfor scope and control framework context
- Read
Applicable state law mapping:
- Determine which state laws apply based on organizational operations and customer base
- Assess applicability for established laws: Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA
- Assess applicability for newer laws: Texas TDPSA, Oregon OCPA, Montana MCDPA, Iowa ICDPA, Delaware DPDPA, New Jersey NJDPA, New Hampshire, Kentucky, Nebraska, Maryland, Minnesota, and others
- Document applicability thresholds per state (consumer count, revenue, data processing volume)
Cross-state requirement comparison:
- Compare consumer rights across states (access, delete, correct, portability, opt-out)
- Identify opt-out vs opt-in consent models per state
- Compare right to cure periods (30 days, 60 days, or none)
- Map enforcement mechanisms (AG only vs private right of action)
- Assess universal opt-out signal requirements per state
Common baseline identification:
- Identify the most restrictive state as the compliance floor
- Map common requirements shared across all applicable states
- Highlight unique or unusual state-specific requirements
- Assess whether a single compliance program can satisfy all states
Unique state requirements:
- Assess Data Protection Impact Assessment (DPIA) requirements by state
- Evaluate profiling and automated decision-making rights per state
- Review sensitive data definitions and consent requirements (varies by state)
- Assess children's data protections by state
- Evaluate data broker registration requirements where applicable
State-by-state compliance matrix:
- Create matrix: state vs requirement category (rights, notice, consent, DPIAs, enforcement)
- Score compliance per state per category
- Identify states with highest compliance gap
- Prioritize remediation by enforcement risk and gap severity
Write the artifact to
.singularskills/compliance/<project>/01-assess/us-state-privacy.mdfollowing the assessment template structure with:- Applicable States — list of states with applicability rationale
- Cross-State Matrix — requirements comparison across all applicable states
- Common Baseline — most restrictive floor requirements
- Unique Requirements — state-specific obligations not covered by baseline
- Per-State Compliance Score — per state, score = (Compliant + 0.5 × Partial) ÷ applicable requirements (N/A excluded), as a percentage
- Gap Analysis — areas where current practices fall short per state
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The US state privacy law assessment written to .singularskills/compliance/<project>/01-assess/us-state-privacy.md. Present a summary to the user highlighting:
- Number of applicable state laws and highest-risk states
- Common baseline compliance score — score = (Compliant + 0.5 × Partial) ÷ applicable common-baseline requirements (N/A excluded), as a percentage
- States with the largest compliance gaps
- Top 3 gaps requiring remediation
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-us-state-privacy","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-us-state-privacy
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.