audit-support-workpaper-requirements
Sub-skill of audit-support: Workpaper Requirements (+2).
Best use case
audit-support-workpaper-requirements is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of audit-support: Workpaper Requirements (+2).
Teams using audit-support-workpaper-requirements should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workpaper-requirements/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How audit-support-workpaper-requirements Compares
| Feature / Agent | audit-support-workpaper-requirements | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of audit-support: Workpaper Requirements (+2).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Workpaper Requirements (+2) ## Workpaper Requirements Every control test should be documented with: 1. **Control identification:** - Control number/ID - Control description (what is done, by whom, how often) - Control type (manual, automated, IT-dependent manual) - Control frequency - Risk and assertion addressed 2. **Test design:** - Test objective (what you are trying to determine) - Test procedures (step-by-step instructions) - Expected evidence (what you expect to see if the control is effective) - Sample selection methodology and rationale 3. **Test execution:** - Population description and size - Sample selection details (method, items selected) - Results for each sample item (pass/fail with specific evidence examined) - Exceptions noted with full description 4. **Conclusion:** - Overall assessment (effective / deficiency / significant deficiency / material weakness) - Basis for conclusion - Impact assessment for any exceptions - Compensating controls considered (if applicable) 5. **Sign-off:** - Tester name and date - Reviewer name and date ## Evidence Standards **Sufficient evidence includes:** - Screenshots showing system-enforced controls - Signed/initialed approval documents - Email approvals with identifiable approver and date - System audit logs showing who performed the action and when - Re-performed calculations with matching results - Observation notes (with date, location, observer) **Insufficient evidence:** - Verbal confirmations alone (must be corroborated) - Undated documents - Evidence without identifiable performer/approver - Generic system reports without date/time stamps - "Per discussion with [name]" without corroborating documentation ## Working Paper Organization Organize testing files by control area: ``` SOX Testing/ ├── [Year]/ │ ├── Scoping and Risk Assessment/ │ ├── Revenue Cycle/ │ │ ├── Control Matrix │ │ ├── Walkthrough Documentation │ │ ├── Test Workpapers (one per control) │ │ └── Supporting Evidence │ ├── Procure to Pay/ │ ├── Payroll/ │ ├── Financial Close/ │ ├── Treasury/ │ ├── Fixed Assets/ │ ├── IT General Controls/ │ ├── Entity Level Controls/ │ └── Summary and Conclusions/ │ ├── Deficiency Evaluation │ └── Management Assessment ```
Related Skills
llm-wiki-audit-feedback-loop
Durable feedback loop for correcting llm-wiki pages without losing the correction to chat history. Use when (1) a human notices a wiki page is wrong, outdated, or contradicts a source, (2) processing the `audit/` inbox of a domain wiki, (3) reviewing what feedback has been resolved vs deferred, (4) needing to leave a comment on a specific text range that survives line- number drift. Implements the anchored-text audit file pattern from lewislulu/llm-wiki-skill, adapted for workspace-hub's domain-wiki layout under /mnt/local-analysis/llm-wiki/wikis/<domain>/. Extends the 5-op model (compile/ingest/query/lint) from research/llm-wiki with the missing `audit` op. Never silently delete feedback — rejected audits stay archived with rejection rationale.
pre-completion-cleanup-audit
Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
provider-session-ecosystem-audit-and-exporters
Build and maintain cross-provider session-log audits for Codex, Codex, Hermes, and Gemini, including exporter design, normalization, and behavioral verification.
orcawave-orcaflex-readiness-audit
Audit the real readiness of digitalmodel OrcaWave/OrcaFlex spec-driven workflows by reconciling workspace-hub issues, source/tests, semantic-equivalence boundaries, and wiki synthesis gaps.
read-only-pre-implementation-audit
Systematic cross-check workflow to validate assumptions before TDD coding begins
provider-audit-bootstrap-and-path-classification
Fix provider-session ecosystem audit failures caused by source-checkout imports and over-aggressive symbolic-path classification.
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
gsd-operational-audit
Audit a repo's live GSD/get-shit-done workflow state against docs, issues, and runtime outputs to find stale issues, automation reliability gaps, parser drift, migration residue, and policy contradictions.
github-issue-label-existence-audit
Prevent GitHub issue creation failures by auditing exact label existence, duplicate titles, and partial-create risk before calling gh issue create.
github-issue-label-audit-and-command-bundles
Safely turn drafted issue bodies into reusable gh issue create commands by auditing repo labels, exact duplicates, and auth first.
orcaflex-spec-audit
Audit, classify, and score OrcaFlex spec.yml files across the model library for quality, schema validity, and structure type categorization.