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

If Claude Skills is new to you

Claude Skills are reusable instruction folders that Claude can load when a task matches the skill description. Current Anthropic help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you will create one private custom skill, upload it in Claude under Customize > Skills, enable it, test that Claude recognizes it, then use it to turn scattered weekly project notes into a Progress, Plans, Problems update. The Claude Skills tool hub is useful further reading, but you do not need to leave this article to run the basic workflow.

What skill you will use in this workflow

You will use a custom skill called weekly-3p-update.

That skill does one narrow job: it turns messy weekly project material into a concise 3P leadership update with three fixed sections: Progress, Plans, and Problems. It is best when the same leader or team expects the same 3P structure every week and you do not want to rewrite the same prompt every Friday.

Before using the skill, prepare the reporting week, project name, audience, and source notes. The skill should organize and clarify the material, not invent missing owners, dates, causes, or progress.

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

• Claude with code execution enabled and access to Skills.
• 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.
• Permission to use the project material in Claude under your organization's AI and data policy.

How to gather the source material

1. Put everything for the week in one folder, one Claude Project, or one clean upload set.
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.

Build the custom skill for this workflow

Create a folder named weekly-3p-update. Inside it, add a file named SKILL.md. Paste the starter content below, then adjust the wording if your team uses specific section rules, escalation language, or length limits.

---
name: weekly-3p-update
description: Standardize messy weekly project notes into a concise Progress, Plans, Problems leadership update with uncertainty markers and support-needed callouts.
---

# Weekly 3P Update

Use this skill when the user wants a weekly Progress, Plans, Problems update from scattered project material such as meeting notes, pasted bullets, email snippets, milestone lists, and blocker notes.

## What this skill should do

- Extract only stated facts from the source material.
- Separate completed work from future work.
- Keep blocker language neutral and factual.
- Mark missing owners, dates, or dependencies as [UNCLEAR] instead of guessing.
- End with one short support-needed or decision-needed line only if the source material supports it.

## Output shape

Return a plain-text update with these exact headings:
1. Progress
2. Plans
3. Problems

## Guardrails

- Do not invent progress.
- Do not merge Progress and Plans.
- Do not hide uncertainty.
- Do not add spin, praise, or blame language.

## Examples

- Turn these notes into a weekly 3P update for leadership.
- Draft a concise Progress, Plans, Problems update from this week's project folder.
- Use the weekly 3P format and flag anything unclear.

Zip the weekly-3p-update folder so the ZIP contains the skill folder at the root. Upload the ZIP in Claude under Customize > Skills, then enable the skill. Do not upload a ZIP that contains loose files at the root without the skill folder.

This starter is only a first draft. If your leader expects exact labels, a fixed word count, or a specific support-needed line, add those rules to SKILL.md before you upload it.

Optional official Anthropic skill

Anthropic's official internal-comms skill is the closest public fit. It covers internal communications such as status reports, leadership updates, project updates, and 3P updates.

Use internal-comms as a shortcut when you want a general internal update pattern. Use the private weekly-3p-update skill when your team needs house-specific 3P rules, specific escalation language, fixed section ordering, or recurring expectations from the same leader.

Why this should be a custom skill, not a one-off prompt

This is repetitive work with a fixed output shape. A custom skill keeps the 3P sections, uncertainty markers, and no-invention rules in one place. That reduces prompt rewrite friction and makes next week's update easier to run with the same standards.

Skill trigger test

After enabling the skill, try these prompts with a small sample note:

• Turn this week's notes into a weekly 3P leadership update.
• Draft a concise status report in Progress, Plans, Problems format.
• Use my 3P update workflow and keep uncertainty visible.
• Convert these project bullets into the weekly leadership update format.

Claude should treat these as weekly-3p-update tasks and produce the three fixed sections. If it does not, tighten the skill description so it names weekly 3P updates, leadership updates, project status reports, and Progress, Plans, Problems.

Numbered workflow steps

1) Gather and clean the source material

Collect the week's notes, meeting bullets, milestone changes, email snippets, and blocker notes. Remove duplicate text, stale status sections, signatures, and any private material leadership should not see.

Create or update leadership-context.txt with:

• project name
• reporting week
• audience
• known deadlines
• recurring leader preferences
• any terms or acronyms Claude should preserve

2) Create, upload, and enable the custom skill

If you have not already done it, create the weekly-3p-update folder, add SKILL.md, zip the folder, upload it in Claude under Customize > Skills, and enable it.

If the skill already exists, open Claude's Skills settings and confirm it is enabled before starting the weekly run.

3) Run a quick trigger test

Use one short prompt before uploading the full source pile:

Use my 3P update workflow to turn this into a weekly leadership update:

Progress: kickoff meeting held, intake form approved
Plans: vendor follow-up next week, draft timeline by Friday
Problems: final budget owner unclear

Check that Claude returns the exact sections Progress, Plans, and Problems and marks the unclear budget owner instead of inventing one.

4) Run the actual workflow with the skill active

Upload or paste the cleaned source material and leadership-context.txt. Then ask:

Use the weekly-3p-update skill to turn these notes into a concise weekly 3P leadership update for [AUDIENCE].

Use only the attached or pasted source material. Keep missing owners, dates, causes, or dependencies visible as [UNCLEAR]. Do not invent progress. End with one support-needed or decision-needed line only if the source material supports it.

If Claude asks for clarification before drafting, answer only with information you can verify.

5) Do a human verification pass

Before sending anything, check:

• Progress only includes completed work.
• Plans only includes future work.
• Problems stays neutral and factual.
• Owners, dates, dependencies, and causes are not invented.
• Sensitive or premature information has been removed.
• Any [UNCLEAR] marker is either resolved by you or left visible for leadership.

6) Save, send, or reuse the result

Save the final 3P, the source note set, and any useful corrections in the same team folder or Claude Project. If Claude missed a recurring rule, update SKILL.md before next week's run so the skill improves over time.

Tool-specific instructions

Claude Skills

• Use the page-specific weekly-3p-update custom skill first.
• Keep internal-comms in mind as a general official public skill for broader internal communications, not as a full replacement for your private 3P rules.
• Anthropic's official skill-creator skill can help draft, test, or refine your custom skill if you want help improving the description, trigger prompts, or instructions.
• For broader setup context, examples, and related Claude Skills workflows, see the Claude Skills tool hub.

Low-friction fallback

If you cannot upload a skill yet, keep the starter SKILL.md text, your best 3P example, and leadership-context.txt in a Claude Project. Paste the skill instructions before each run. This is less reliable than a real skill because you must remember the setup every week.

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: update SKILL.md to say completed work belongs only under Progress and future work belongs only under Plans. Rerun the trigger test before using real notes.

The update sounds too long or too managerial

Fix: add a length rule to the skill. For example: "Keep the finished 3P between 150 and 250 words unless the user asks for more detail."

Important blocker detail disappears

Fix: add the missing blocker detail to the verified source material, not just to the prompt. Then rerun the workflow with the skill active.

Claude invents an owner, date, or cause

Fix: stop and correct the output before sending. Update the skill guardrails to mark missing owners, dates, dependencies, or causes as [UNCLEAR].