CREATE THE SKILL
Attach 01-Report-Brief.txt, 02-Example-Report.docx and 03-Example-Report.pdf.

Create a reusable Claude Skill named weekly-project-report from the attached brief, Word template and PDF visual reference.

The skill must turn new weekly project notes into an editable branded Word report and a matching PDF. Use the Word template as the starting document and the PDF to check the layout. Preserve the branding, status strip, decision panel, action table and reviewer checklist. Adapt the status colour to the supplied status. Use only the new notes for project facts; the example supplies layout and tone only.

Create a downloadable ZIP with one top-level folder named weekly-project-report. Include:
- SKILL.md with YAML name and description fields. Keep the description under 200 characters and say what this skill does and when to use it.
- references/report-brief.txt containing the attached brief.
- assets/example-report.docx containing the attached Word template.
- assets/example-report.pdf containing the attached visual reference.

Make SKILL.md explicitly read the brief and use both assets. Allow local code and document tools to create and check DOCX and PDF files. Preserve the embedded fonts where possible. Keep all evidence rules from the brief, including missing owners, unapproved requests and the distinction between forecast total and approved budget. Do not instruct the skill to browse for facts, send messages or update external systems.

A forecast total may exceed actual spend plus commitments because future costs may not yet be committed. Do not label that difference an error merely because it exists. Ask for a breakdown only if needed for a decision; do not invent one. Apply that rule to any script checks as well as the written instructions.

Do not include weekly source notes, a prewritten North Quay report or expected test answers. Do not package this conversation or the recording guide. Include any small supporting script only if it is needed for this document workflow; it must work with new project facts.

Show me the file list and SKILL.md text for review, and provide the skill ZIP to download. Do not claim it has been installed or tested in my account.

RUN EACH WEEK
Start a fresh chat. Attach only 04-Week-1-Notes.txt, then repeat in another fresh chat with only 05-Week-2-Notes.txt.

Use weekly-project-report to create this week's sponsor report from the attached notes. Return the branded Word document and matching PDF.

REPAIR THE OBSERVED BUDGET CHECK
Only if your generated skill contains that rule. Attach the skill, original report and the relevant notes.

Review the attached skill, original report and source notes. The checking rule must not treat forecast total minus spend and commitments as an error merely because the difference is non-zero. Future costs may not yet be committed.

Find and correct that rule in both SKILL.md and any supporting script. Preserve the separate check comparing forecast total with approved budget, and keep all approval and missing-owner rules. Do not hardcode the demonstration project's figures.

Show the changed rule and provide a revised skill ZIP. Test with fictional cases where forecast is above spend plus commitments but within budget, and where it exceeds the approved budget. Report what you actually checked. Do not claim this is verified in my account.
