Produces a prioritized issue memorandum reviewing draft voluntary self-disclosures for completeness, accuracy, citation hygiene, intent-characterization consistency with the evidentiary record, missing concurrent disclosure obligations, and cross-document internal consistency.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill review-draft-voluntary-self --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Review Draft Voluntary Self?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-review-draft-voluntary-self)More formats (shields.io, HTML) on the badges page.
---
name: its-review-draft-voluntary-self
task_id: international-trade-sanctions/review-draft-voluntary-self
description: Produces a prioritized issue memorandum reviewing draft voluntary self-disclosures for completeness, accuracy, citation hygiene, intent-characterization consistency with the evidentiary record, missing concurrent disclosure obligations, and cross-document internal consistency.
activates_for: [planner, solver, checker]
---
# Skill: Review Draft Voluntary Self-Disclosure for Completeness, Accuracy, and Strategic Concerns
## 1. Subject-matter triage (only if applicable)
- This task is an issue-spotting and advisory review of draft voluntary self-disclosures and supporting records, not a rewrite of the filings themselves.
- Treat each disclosure package separately unless the instructions or source set make clear they are part of one coordinated submission.
- If the source set includes more than one disclosure draft, enumerate the drafts and review each for internal consistency before comparing them against one another.
- If the record includes transaction tables, correspondence, internal investigation materials, or prior drafts, treat them as the controlling factual record for verification.
- If the package involves multiple regulatory tracks, identify each track up front and assess whether a filing duty exists on each track before reaching strategy conclusions.
## 2. Failure modes the skill is correcting
- Reading the disclosure at a narrative level without verifying each stated amount, count, date, party reference, and transaction description against the underlying record.
- Treating a characterization such as inadvertent, unintentional, or isolated as a drafting preference instead of testing it against contemporaneous communications and investigation findings.
- Missing separate reporting duties that arise from the same event and should be addressed alongside the main disclosure.
- Accepting regulatory citations as drafted without checking part, section, appendix, supplement, or other pinpoint references.
- Reviewing each draft in isolation and missing contradictions across drafts, attachments, or supporting summaries.
- Assessing mitigation language without checking whether corrective action and preventive measures are actually supported by the factual record.
- Failing to distinguish between a factual correction, a strategic concern, and a missing disclosure obligation in the final memorandum.
## 3. Legal frameworks / domain conventions that apply
- Voluntary self-disclosure practice requires a complete, accurate, and credible factual narrative, with enough detail to permit agency review and mitigation analysis.
- Sanctions and export-control disclosure practice commonly turns on transaction dates, parties, goods or services, amounts, and the number of events; verify each stated figure against the source record before relying on it.
- Separate reporting obligations may arise from blocked, rejected, or otherwise interrupted transactions, and from other specialized reporting regimes that sit alongside the main disclosure.
- Intent characterization must be supported by the contemporaneous record; a statement that conduct was inadvertent, isolated, or unintentional is risky if internal communications show awareness of the issue before or during the conduct.
- Boycott-related instructions can trigger distinct reporting duties; review purchase orders, instructions, and related records for triggering language and confirm whether any required report was made.
- Time sensitivity matters: review the age of the conduct against any applicable limitations period or agency timing posture, because older events may change the strategic value of disclosure.
- Citation hygiene is a credibility issue, not a formatting issue; incorrect references can undercut trust in the entire submission.
- Corrective action analysis should connect the stated fix to the identified root cause; generic remediation without a causal link is weak.
## 4. Analytical scaffolds
1. Enumerate each disclosure draft, each violation cluster, and each separate reporting regime potentially implicated; then review them one by one rather than merging them into a single pass.
2. For each stated amount, event count, or other quantified fact, independently recalculate from the source record and compare the draft’s figure to the record.
3. For each factual assertion in the narrative, check the cited source documents for direct support and identify unsupported or overstated statements.
4. For each intent-related characterization, review contemporaneous emails, notes, interview summaries, and investigation findings for evidence of awareness, warning signs, or escalation before the conduct.
5. For each event that may have triggered a separate notice or report, confirm whether the filing duty arose and whether a filing was made.
6. For each citation in the draft, verify the legal authority and pinpoint reference against the governing statute, regulation, or agency guidance.
7. For each date-sensitive issue, test the timeline against the applicable limitations or timing considerations and note any strategic consequence.
8. For each corrective action statement, test whether the remedial step addresses the root cause, the affected process, and the prevention gap.
9. For each cross-document inconsistency, identify which document should control, why the conflict matters, and how it affects credibility or strategy.
## 5. Vertical / structural / temporal relationships (only if applicable)
- Where one transaction, instruction, or communication sequence affects multiple disclosures, assess the dependencies in order of occurrence.
- Where later drafts revise earlier facts, check whether the revision resolves the discrepancy or creates a new inconsistency.
- Where a blocked, rejected, or boycott-related event sits inside a broader transaction pattern, determine whether the event is a standalone issue or part of a larger disclosure cluster.
- Where internal awareness develops over time, distinguish between pre-event knowledge, contemporaneous awareness, and post-event remediation; the timing difference is central to intent characterization.
- Where old and new conduct are mixed together, separate the time periods so the memorandum does not overgeneralize one period’s facts to another.
- Where multiple reporting duties arise from the same facts, identify the primary filing and any concurrent filing or notice obligations in the order they would have been triggered.
## 6. Output structure conventions
- Produce a prioritized issue memorandum, not a narrative essay.
- Define one ordinal severity scale at the top and apply it uniformly to every issue entry.
- Lead each issue entry with: issue summary, severity, source support, governing authority, and why it matters.
- For each issue, include the factual discrepancy or gap, the controlling authority or disclosure convention, the supporting source citation, and the downstream consequence for the client.
- Include a separate section for corrected figures or counts where a numerical mismatch exists, with the source-based calculation shown in a concise form.
- Include a separate strategic concerns section for intent characterization, timing or limitations concerns, and any missing concurrent disclosure obligations.
- End with a Recommended Actions block that uses imperative verbs, identifies the responsible role, and gives a timing anchor tied to the disclosure process or regulatory milestone.
- When multiple drafts are present, include a short cross-document consistency section identifying conflicts that should be resolved before filing.
- Avoid vague labels; every entry should state the issue, the basis, the severity, and the recommended fix in plain terms.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!