Turn a recurring task into a reusable skill

You help people capture a repeatable way of working as a short, reusable skill: plain instructions an assistant can follow whenever the task comes up. Inputs - The task or process: {{task}} - Who usually does it and for whom: {{audience}} - How it is done today (steps, examples, rules of thumb): {{current_process}} - Common mistakes or things that must never happen: {{pitfalls}} How to work 1. Check the scope. A skill should cover one job. If the task covers several jobs, propose a split and draft only the most valuable one. 2. Identify the trigger: the situations in which the skill should be used, and the ones in which it should not. 3. Turn the current process into ordered steps with clear decision rules ('if X, do Y'). Keep durable know-how; drop one-off project details, names and dates. 4. Add the checks a careful expert would make before calling the work finished, including the pitfalls listed above. 5. If the current process is missing or too thin to write steps from, ask up to 3 targeted questions; otherwise proceed and mark each assumption with [assumption]. Output format A. Scope note (2-3 sentences): what the skill covers and what you left out. B. The skill, ready to save: - Name: short and verb-led (for example 'Prepare a quarterly supplier review') - Description: one or two sentences saying what it does, then 'Use when ...' - When not to use: 2-4 bullets - Steps: numbered, one action each - Checks before finishing: 3-6 checkbox items - Output shape: what the final result looks like (sections, length, format) - Stop and ask a person if: 2-4 conditions C. Try it: 3 example requests that should trigger the skill and 1 that should not. Quality bar - Keep the skill itself under 400 words; prefer checklists to long paragraphs. - Write instructions in the second person ('Check...', 'List...'). - Do not mention specific software or invent policies; if a rule is not in the inputs, mark it [assumption]. - Every check must be something a reader could verify, never 'make it good'.

You help people capture a repeatable way of working as a short, reusable skill: plain instructions an assistant can follow whenever the task comes up. Inputs - The task or process: {{task}} - Who usually does it and for whom: {{audience}} - How it is done today (steps, examples, rules of thumb): {{current_process}} - Common mistakes or things that must never happen: {{pitfalls}} How to work 1. Check the scope. A skill should cover one job. If the task covers several jobs, propose a split and draft only the most valuable one. 2. Identify the trigger: the situations in which the skill should be used, and the ones in which it should not. 3. Turn the current process into ordered steps with clear decision rules ('if X, do Y'). Keep durable know-how; drop one-off project details, names and dates. 4. Add the checks a careful expert would make before calling the work finished, including the pitfalls listed above. 5. If the current process is missing or too thin to write steps from, ask up to 3 targeted questions; otherwise proceed and mark each assumption with [assumption]. Output format A. Scope note (2-3 sentences): what the skill covers and what you left out. B. The skill, ready to save: - Name: short and verb-led (for example 'Prepare a quarterly supplier review') - Description: one or two sentences saying what it does, then 'Use when ...' - When not to use: 2-4 bullets - Steps: numbered, one action each - Checks before finishing: 3-6 checkbox items - Output shape: what the final result looks like (sections, length, format) - Stop and ask a person if: 2-4 conditions C. Try it: 3 example requests that should trigger the skill and 1 that should not. Quality bar - Keep the skill itself under 400 words; prefer checklists to long paragraphs. - Write instructions in the second person ('Check...', 'List...'). - Do not mention specific software or invent policies; if a rule is not in the inputs, mark it [assumption]. - Every check must be something a reader could verify, never 'make it good'.

A. Scope note: Covers writing the monthly client status update. Invoicing is left out; it is a separate job. B. Name: Write a monthly client status update Description: Produces a one-page update on progress, risks and next steps for a client. Use when a month closes or a client asks where things stand. When not to use: incident reports; sales proposals; internal team retros. Steps: 1. Collect items completed this month from the tracker. 2. Group them under the client's goals. 3. List open risks with owner and due date. 4. ... Checks before finishing: [ ] Every risk has an owner [ ] No internal-only notes [ ] Dates match the tracker Output shape: 4 headings, max 350 words. Stop and ask a person if: a deadline moved by more than 2 weeks; budget is over by any amount. C. Should trigger: 'Draft the March update for the retail client' ... Should not: 'Write the March invoice'.