Set up
Try a plugin
The Finance plugin ships with /sox-testing and other close and compliance skills as a starting point, already structured to list the controls to test and build testing workpapers. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.
/sox-testingGenerate SOX sample selections, testing workpapers, and control assessments.Connect your tools
Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access(opens in new tab).
Add a connector(opens in new tab) for each tool you want Claude to use.
Set your working folder
Drag the files you'll use (your walkthrough notes, prior-year narrative, the RCM template, system screenshots) into one folder on your machine, then give Claude access to it(opens in new tab) in the Claude desktop app. Claude reads from it and writes the narrative, matrix, and flowchart back to it. If you'll document several processes this cycle, create a project(opens in new tab) from the parent Controls folder so the template and house style stay attached.
The prompt
Copy this into Claude
Here's how this process runs. Write the process narrative in our standard format, build the risk and control matrix mapping each risk to its control, owner, and frequency, and draw the flowchart. Flag any step where a control looks missing or a segregation of duties issue shows up.
Why this works
Start from the current state. "Here's how this process actually runs" anchors the documentation in operational reality, not last year's narrative, so the matrix matches what auditors will walk.
Ask for related outputs in one prompt. Naming the narrative, the matrix, and the flowchart in one prompt keeps them consistent with each other; the same step number means the same thing in every file.
Ask it to flag what's missing. Asking to "flag any step where a control looks missing" so you can find the gaps while documenting, when they're still easy to fix.
Let the working folder supply the format. Your RCM template and prior-year narrative sit in the working folder, so "our standard format" resolves to your actual columns and headings without you pasting them in.
Get a better draft
Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.
Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.
Make Claude work for you
Tell Claude your own rules for this task, such as your RCM columns and your control-ID scheme, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.
Make what we've done in this task so far into a skill called /controls-package.
Review the skill, and save it if Claude hasn't already.
Make it repeatable
Run it on every walkthrough
Give Claude access to the parent Controls folder, where process owners drop their walkthrough notes. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /controls-package runs on each new walkthrough added to the Controls folder.
Set up a scheduled task for weekdays at 9am: check Controls for any new walkthrough file, run /controls-package against it, and write the narrative, RCM, and flowchart to a subfolder named for the process.
Runs /controls-package on every new walkthrough in Controls and writes the narrative, matrix, and flowchart to a process subfolder.
To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.
Share with your teammates
Your /controls-package skill now carries your RCM columns, your control-ID scheme, and your narrative voice. Share it so every process owner produces the same audit-ready package, and internal audit sees one consistent format across the cycle.