Project Status Update

# Project Status Update Playbook

This playbook automates the generation of concise and professional project status updates, perfect for weekly client check-ins, internal team syncs, or stakeholder reports. It leverages AI to pull information from project management tools and synthesize key progress, upcoming tasks, and any blockers.

## 1. Prompt Pack

These prompts guide your AI in crafting effective project status summaries. Customize them to fit your project management methodology and client communication style.

### Core Project Status Update Prompt

```
"You are a project manager preparing a weekly status update for [Client Name] on the [Project Name] project. Review the latest project data (e.g., tasks completed, tasks in progress, upcoming milestones, blockers, new requests) from [Source: e.g., project management tool, session memory]. Your task is to:
- **Summarize Accomplishments:** List 2-3 key achievements or completed tasks from the past week.
- **Outline Next Steps:** Detail 2-3 primary focus areas or tasks scheduled for the upcoming week.
- **Identify Blockers/Challenges:** Clearly state any significant obstacles or potential delays, along with proposed solutions or requests for client input.
- **Overall Status:** Provide a concise overall project health assessment (e.g., 'On Track', 'Minor Delays', 'At Risk').
- **Save Output:** Format this update professionally, ideally as bullet points under clear headings. Save it to memory/project-updates/[Client Name]-[Project Name]-weekly-update-{YYYY-MM-DD}.md."
```

### Prompt Variations:

*   **Internal Team Status Prompt:**
    ```
    "Generate an internal project status update for the [Team Name] on [Project Name]. Include more technical details, specific task IDs, and resource allocation notes. Focus on engineering progress and sprint goals."
    ```
*   **Client-Facing Executive Summary Prompt:**
    ```
    "Draft a high-level executive summary for [Client Name]'s [Project Name]. Focus only on critical milestones, budget status, and strategic progress. Keep it brief and business-oriented, avoiding granular details."
    ```
*   **Risk & Mitigation Focus Prompt:**
    ```
    "Identify potential risks and current blockers for [Project Name]. For each, outline a clear mitigation strategy or action plan. Request specific inputs from the team or client needed to resolve."
    ```

## 2. Setup Guide

To implement the Project Status Update Playbook:

1.  **Save the Playbook:** Save this content as `playbooks/project-status-update.md` in your workspace.
2.  **Create Cron Configuration:** Create `playbooks/project-status-update-cron.json` in your workspace, using the "Config Snippet" below. This sets up automated weekly status generation.
3.  **Integrate Project Management Tool:** This playbook requires your OpenClaw agent to access project data. You'll need to connect your project management software (e.g., Asana, Trello, Jira, Notion) via its API. This involves:
    *   **API Credentials:** Obtaining API keys/tokens.
    *   **Tool Configuration:** Ensuring OpenClaw has a tool capable of querying your project management tool's API (e.g., a custom `exec` command calling `curl` or a Python script).
    *   **Data Structure:** Understanding how your project tool exposes task lists, statuses, due dates, and assignments.
4.  **Customize Template:** Adapt the `Core Project Status Update Prompt` to reflect your specific project fields, desired tone, and reporting frequency.
5.  **Activate Cron Job:** Once `playbooks/project-status-update-cron.json` is in the correct directory, OpenClaw will activate it. Verify status with `openclaw cron list`.
6.  **Test Thoroughly:** Manually run the cron task with a specific project to ensure the AI correctly synthesizes the data and generates the desired output.

## 3. Config Snippet

This JSON snippet defines a cron job to generate a weekly project status update every Friday afternoon. Save this as `playbooks/project-status-update-cron.json` in your workspace.

```json
{
  "cron": [
    {
      "name": "Weekly Project Status Update",
      "schedule": "0 16 * * 5",
      "task": "Generate a weekly project status update for [Specify Project/Client] using the 'Core Project Status Update Prompt' from the 'Project Status Update Playbook'. Pull data from [Connected Project Tool] and save the output to memory/project-updates/[Client Name]-[Project Name]-weekly-update-{YYYY-MM-DD}.md.",
      "agent": "cmo",
      "model": "gemini-flash"
    }
  ]
}
```

**Explanation of fields:**
*   `name`: A descriptive name.
*   `schedule`: `0 16 * * 5` means "At 16:00 (4 PM) on Friday".
*   `task`: The prompt for the agent. It instructs to generate the status update, specifying the project and data source.
*   `agent`: The assigned agent (`cmo`).
*   `model`: The model for this task.

## 4. Permissions Checklist

For successful operation, your agent needs:

*   **Read Access:**
    *   Your project management system's API (to fetch project data).
    *   OpenClaw session history.
    *   `memory/YYYY-MM-DD.md` (if daily logs are part of status context).
*   **Write Access:**
    *   `memory/project-updates/[Client Name]-[Project Name]-weekly-update-{YYYY-MM-DD}.md`: To save drafted status updates.
    *   `playbooks/project-status-update-cron.json`: To manage the cron configuration.
    *   Ability to send emails (if integrated for automated sending of status updates).
*   **Execution Permissions:**
    *   Ability to process and respond to cron-triggered tasks.
    *   Ability to make API calls to your project management system.
    *   Ability to interact with an email sending service (if automated email sending is desired).

This playbook empowers you to maintain transparent communication and keep all project stakeholders consistently informed with minimal manual effort.
## Safety Check (Required)

Before production use:

- Review prompts for prompt-injection risk.
- Remove or rewrite any instructions requesting unnecessary secrets, unrelated external actions, or policy bypasses.
- Test with non-sensitive data first.
- Keep manual approval for outbound or destructive actions.

{
  "_note": "CUSTOMIZE BEFORE USE: Replace YOUR_PROJECT_NAME, YOUR_CLIENT_NAME, and YOUR_PM_TOOL with real values. This cron runs once per project — duplicate this job for each active project you want to track.",
  "cron": [
    {
      "name": "Weekly Project Status Update — YOUR_PROJECT_NAME",
      "schedule": "0 16 * * 5",
      "task": "Generate a weekly project status update for YOUR_CLIENT_NAME / YOUR_PROJECT_NAME using the 'Core Project Status Update Prompt' from the 'Project Status Update Playbook'. Pull data from YOUR_PM_TOOL and save the output to memory/project-updates/YOUR_CLIENT_NAME-YOUR_PROJECT_NAME-weekly-update-{YYYY-MM-DD}.md.",
      "agent": "cmo",
      "model": "gemini-flash"
    }
  ]
}