Documenting Laserfiche workflows is one of those tasks everyone (including me!) puts off. I built a Claude Code skill that does it automatically; drop in your .wfi file and get two HTML docs: a plain-language guide for staff and a full technical reference for admins.
It produces two html docs:
- End-User Guide -- plain-language explanation for staff who just need to know what the workflow does
- Technical Reference -- full activity map, token inventory, field inventory, permissions, and troubleshooting for admins
It also flags potential issues: unused parameters, disabled activities, misconfigured email subjects...things you might not catch until something breaks.
Your prompts can be tailored to whatever you want such as targeting specific users or departments. Here's some sample prompts to get you started:
- "Analyze workflow.wfi and generate documentation"
- "Create documentation for this Laserfiche workflow. I need to share it with non-technical staff in our assessor's office."
- "I just inherited this workflow from the previous admin. Can you explain what it does and flag anything that looks misconfigured?"
The skill is free and open source on GitHub: https://github.com/ABEVIntegrations/lfdocbuilder
It works with Claude Code CLI or Claude.ai Projects (web); point it at your .wfi file, run a prompt, done. Instructions are in the README.
What's your current process for documenting workflows? Always looking to improve the skill.