Given the nature of my work I can't give specific details of it. But I can tell you about my current project where I'm transforming my tasks into a cohesive workflow.
Before I hade a monolitic file with all the instructions, but now I created a main .md-file (skill) with general instructions and subsequent instruction files for each activity.
When validating equipments or processes, usually we start with an URS, (User requirement specification) after that a FAT, SAT, IQ, OQ, PQ and PV. Can explain each one if somene is interested.
The FAT/SAT documents should be identically and the IQ and OQ are actually included in the FAT so when I create the FAT, three more documents are automatically generated.
Each skill file covers one document type (IQ,OQ, PQ, SAT, URS, PV protocol/report) and contains mandatory conduct rules, fixed section skeletons with exact table column definitions, language constraints, and a review checklist. Instead of re-prompting every session, I load the relevant skill and Claude follows the established structure.