Claude Code Guide
বাংলায় পড়ুন

15 min / intermediate / 4 steps

Build a Weekly Status Report Generator

Pull from your projects and generate a stakeholder-ready status report in seconds.

Nobody likes writing status reports. But everyone needs them. Let's build a skill that gathers context from your projects and generates a clean, stakeholder-ready report in seconds. You'll go from "I need to write my weekly update" to having it done before your coffee gets cold.

follow along in

You need: A Claude account. Open claude.ai in a browser, or the Claude desktop app.

  1. step 01 / 04

    Set up memory with your project context

    First, give Claude the context it needs, including your projects, your team, and what stakeholders care about. This goes in your CLAUDE.md.

    Prompt
    I want to create a weekly status report generator. My context: I'm a PM reporting to leadership weekly. Projects: Alpha (auth redesign, Q2 deadline), Beta (mobile app v2, in beta), Gamma (API perf, ongoing). Stakeholders: VP Product wants high-level + risks, Engineering Director wants technical detail, CEO wants one sentence per project.

    what you should see

  2. step 02 / 04

    Create the weekly-status skill

    This skill defines the exact structure of your status report. It tells Claude what sections to include, what tone to use, and how to handle missing information.

    Prompt
    Here's my report format: Weekly status sent every Friday. Structure: TL;DR (one sentence per project with 🟢/🟡/🔴 status), per-project section (this week / next week / risks), decisions needed at the bottom. Rules: scannable, concrete numbers, no vague progress descriptions, bad news in Risks not buried.

    what you should see

  3. step 03 / 04

    Run it and see the report

    Now just tell Claude what happened this week. You can be as messy as you want, bullet points, half-sentences, whatever. The skill handles the formatting.

    Prompt
    Generate my weekly status. Here's what happened: - Alpha: finished password reset, started SSO. SSO more complex than expected, might need extra sprint. - Beta: 200 beta testers, crash rate 0.3%. Critical Android push notification bug. - Gamma: p95 reduced from 800ms to 340ms. Still working on search endpoint.

    what you should see

  4. step 04 / 04

    Customize the output format

    Maybe your team uses Slack. Maybe you want a Confluence-friendly version. Tweak the skill to output in whatever format your team actually reads.

    Prompt
    Give me the same report but formatted for Slack. Short, emoji status indicators, under 500 characters per project.
    markdown
    # Add to your weekly-status.md skill:

## Output Variants
When asked for "slack format":
- Use Slack markdown (bold with *, not **)
- Add emoji reactions as status indicators
- Keep it under 500 characters per project
- End with a thread-friendly "questions? reply here"

When asked for "email format":
- Use a professional subject line
- Start with "Hi team,"
- Attach the detailed report as a quote block
- End with "Let me know if you have questions"

    what you should see

go deeperBuild your daily practice with Claude Code

Tell someone what you built

Just finished "Build a Weekly Status Report Generator" on Claude Code Guide. Took about 15 min, and it's free: https://claudecodeguide.dev/tutorials/weekly-status

Share on LinkedIn

New guides, when they ship

One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.

Or read Product Field Notes, the Substack