How to Use Claude Skills to Turn Scattered Project Notes Into a Weekly 3P Leadership Update

Warning: If your notes mention confidential budgets, personnel issues, customer disputes, or regulated information, only use Claude in a setup your organization has approved.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. For curated examples, see the Claude Skills tool hub and the Anthropic Workflows series.

Problem and who this is for

You have weekly project fragments everywhere: meeting bullets, half-finished status notes, blocker lists, deadline reminders, and maybe a few pasted Slack or email snippets. Leadership does not want the raw pile. They want one clean update that says what moved, what is next, and what is stuck.

This workflow is for office admins, executive assistants, coordinators, operations staff, and project leads who need a consistent weekly Progress, Plans, Problems update without rewriting the same structure from scratch every Friday.

Prerequisites

• A paid Claude plan if you want to use the example Skills available in Claude.ai.
• Your weekly source material in any mix of these formats:
  • meeting notes in DOCX, PDF, or pasted text
  • email summaries or copied thread excerpts
  • milestone lists or task exports
  • a rough note with blocker updates
• A standard 3P audience. Example: director, chief of staff, department lead.

How to gather the source material

1. Put everything for the week in one folder or one Claude Project.
2. Rename messy files so the names tell Claude what they are. Example: 2026-03-23-kickoff-notes.docx, vendor-delay-email.txt, milestone-list.xlsx.
3. Convert anything awkward into a simple readable format before upload. Plain text, PDF, DOCX, and CSV are easier to review than screenshots of tiny text.
4. Strip out obvious junk before you start. Remove repeated signatures, boilerplate disclaimers, duplicated bullets, and old status sections you do not want copied forward.
5. Make one short plain-text note called leadership-context.txt that states the project name, reporting week, and the three or four things leadership usually cares about.

Numbered workflow steps

1) Load or select the right Skill pattern

Use a Claude Skills workflow based on the public internal-comms skill. That skill is designed for internal communications like 3P updates, leadership updates, FAQs, status reports, and incident reports. In practice, that means Claude already has a strong pattern for concise internal reporting.

If you prefer a private version, create your own custom skill later. For the first run, just use the built-in example skill path or the pattern from the repository.

2) Ask Claude to extract facts before it writes anything

Do not jump straight to the finished 3P. First, make Claude separate facts, pending items, and uncertainties.

{
  "task": "Extract structured weekly status inputs for a 3P update",
  "input": {
    "source_material": [
      "ATTACHED FILES OR PASTED NOTES",
      "leadership-context.txt"
    ],
    "reporting_window": "PASTE WEEK OR DATE RANGE HERE",
    "project_name": "PROJECT NAME HERE"
  },
  "rules": [
    "Use only what is present in the source material.",
    "Do not infer progress if it is not explicit.",
    "Keep blocker language neutral and factual.",
    "If a date, owner, or dependency is unclear, mark it [UNCLEAR].",
    "Separate completed work from in-progress work."
  ],
  "output": {
    "progress": "Bullets with completed items and supporting evidence",
    "plans": "Bullets with next-step items, owners, and dates if stated",
    "problems": "Bullets with blockers, risks, or dependencies",
    "open_questions": "Anything that needs human confirmation before the 3P is sent"
  }
}

3) Do a 90 second human cleanup pass

Fix names, dates, project codes, and jargon. Delete anything leadership should not see yet. Add one-line context where a bullet would be confusing without background.

4) Generate the finished 3P in your house style

{
  "task": "Write a weekly 3P leadership update from verified status inputs",
  "input": {
    "verified_status_input": "PASTE CLEANED OUTPUT FROM STEP 2",
    "audience": "EXAMPLE: VP Operations",
    "tone": "concise, direct, calm",
    "length_target": "150 to 300 words"
  },
  "rules": [
    "Use the exact 3P structure: Progress, Plans, Problems.",
    "Keep each section brief and easy to skim.",
    "Do not invent owners, dates, or causes.",
    "If an item is uncertain, keep the uncertainty visible.",
    "End with 1 short line naming the top decision or support needed, if any."
  ],
  "output_format": {
    "type": "plain_text",
    "headings": [
      "Progress",
      "Plans",
      "Problems"
    ]
  }
}

5) Save the final version where next week's update can reuse it

Keep the prompt, your leadership-context.txt, and one or two good examples in the same Claude Project or team handoff folder. That is what turns this from a one-off trick into a repeatable admin workflow.

Tool-specific instructions

Claude Skills

• If Claude Skills is unfamiliar, read the Claude Skills explainer page in the site's Tools menu first.
• The public skills repository says the example skills are already available to paid Claude.ai plans. That is the fastest starting path for this workflow.
• Claude's help also documents private custom skill upload as a ZIP file if you want a team-specific version later.
• The internal-comms skill is the best model for this article because its instructions explicitly cover 3P updates, leadership updates, status reports, FAQs, and incident reports.

Low-friction fallback

If you do not want to build or upload a skill yet, run the same prompts in a Claude Project and keep your example 3P plus leadership-context.txt inside the project. You lose the cleaner skill packaging, but the result is still usable.

Quality checks

1. Every Progress bullet describes something already done, not something merely discussed.
2. Every Plans bullet has a next action and keeps [UNCLEAR] markers where ownership or dates are not explicit.
3. Every Problems bullet states the blocker or risk without blame language.
4. Nothing in the final 3P depends on information that only existed in your head and not in the source material or your manual verification pass.

Common failure modes and fixes

Claude merges Progress and Plans together

Fix: rerun Step 4 and tell Claude to keep completed items only under Progress and future work only under Plans.

The update sounds too long or too managerial

Fix: tighten the length target to 150 to 200 words and ask for one bullet per material point rather than narrative paragraphs.

Important blocker detail disappears

Fix: add that detail during the human cleanup pass, then rerun Step 4 from the verified input instead of from the raw notes.

Sources Checked

• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• Anthropic Claude Help Center: How to create custom Skills (accessed 2026-03-23) https://support.claude.com/en/articles/12512198-how-to-create-custom-skills
• GitHub: elliepetalmedia/skills README (accessed 2026-03-23) https://github.com/elliepetalmedia/skills
• GitHub: internal-comms skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/internal-comms

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Cowork availability, mobile dispatch requirements, project behavior, and supported setup paths.