Summarise a long standard or customer spec into the clauses that matter
Claude reads the whole document and pulls out what your part and your process must meet: requirements, tests, deadlines and records, each with its clause number.
Safe versionEngineeringWhen you need it
Set it up3 steps
Open the Claude desktop app and sign in with the Claude account you use for work. On a personal Free, Pro or Max plan, chats can be used for training unless you switch off SettingsPrivacyHelp improve Claude.
No account yet? Ask your manager.
Where things are in Claude
- CustomizeConnectors In Claude's left sidebar: connect your email and files.
- /schedule Type it in a new Cowork task to run a prompt on a schedule.
- Scheduled In Claude's left sidebar: what runs, to pause or change it.
- Put the spec in a Drive folder called Specs without its drawings and technical annexes (save the text part as its own file if they come bundled), with a short note on the part and the process it is for.
- Connect Google Drive under CustomizeConnectors, open Cowork and paste the prompt.
- Check each requirement against the clause it quotes before you rely on it.
Set this up on your computer: the Claude desktop app runs it.
The prompt
- Taken out by a company rule: Read the specification or standard in my "Specs" folder, with the note next to it on our part and process. Write the result as a new Google Doc in the Specs folder.Read the specification or standard in my "Specs" folder, with the note next to it on our part and process. Use its text and tables only: do not open drawings, figures, CAD files or technical annexes, and do not describe what they show. Where a clause points to one, write [SEE: its number] instead. Write the result as a new Google Doc in the Specs folder.safe version
- 1. Make a table of every requirement that applies to us: clause number, the requirement in one line, how it is checked (test, inspection or record), and how often.
- 2. List the deadlines, approvals and records it asks for, such as the approval level, how long records are kept, and when the customer must be told of a change.
- 3. Mark the clauses that look different from how we work today, or are unusual for a document like this.
- 4. Write the questions to put to the customer where a clause is unclear.
- Quote the exact words of any clause you flag. If a clause is unclear, say so instead of interpreting it.
- Company rule: never put technical drawings into this task. If an email or file contains them, skip that part and tell me.company rule
Kept out of AI
- Technical drawingsKept out
- Safe version. Reads the spec's text and tables, saved without its drawings and technical annexes. Figures are skipped and named by number.
What you get
A requirements table with clause numbers, the clauses that differ from how you work today, and questions for the customer.
Get this workflow for your team
Two minutes each: everyone gets a plan of ready workflows like this one, inside your company's rules.
Your manager sees progress and hours. Never what Claude reads or writes.
FirstPrompt's workflow library adapts parts of Anthropic's knowledge-work-plugins (Apache-2.0), rewritten by FirstPrompt. Source and licence