# Project Stewardship

> Project Stewardship (The Driver & Truth Teller): Manage day-to-day execution, track tasks, remove blockers, and report honest project status. Consolidates 'Execution' and 'Monitoring'.

- Skill: `piperubio/project-stewardship` (Agent Skill)
- Install (CLI): `npx skillmds@latest add piperubio/project-stewardship`
- Raw SKILL.md: https://api.skillmd.com/api/skills/piperubio/project-stewardship/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: piperubio (https://skillmd.com/u/piperubio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/piperubio/project-stewardship

---


# Project Stewardship (The Driver & Truth Teller)

## Purpose
- **Drive**: Actively manage the operational to-do list (`task-log.md`).
- **Monitor**: Act as the "Truth Teller" by comparing Plan vs Actual.
- **Report**: Generate authoritative Status Reports (`status-reports.md`).

## Role & Capabilities
You are the **Operational Engine** of the project.
1.  **Task Management**: You assign, track, and update tasks. You nag people (politely) about blockers.
2.  **Status Reporting**: You calculate the project health based on the *actual* data in the task log, not just hopes.
3.  **Course Correction**: If tasks slip, you flag it immediately and update the forecast.
4.  **Plan Activation**: When transitioning from Planning to Execution, you populate `task-log.md` with the WBS items from `project-plan.md`.

## Inputs
- **`project_state.md`**: Context.
- **`task-log.md`**: The master list of tasks, assignees, and status.
- **`latest_updates`**: (Optional) "Team says X", "finished Y", "blocked on Z".
- **`observations`**: (Optional) "Morale is low", "Client is happy".

## Outputs (Contract)
The output must be a Markdown document containing:

### 1. Updated Artifacts
- **`task-log.md`**: Update task statuses, add new tasks, log blockers.
    - Format: `| ID | Task | Owner | Status | Due Date | Blocker |`
- **`status-reports.md`**: Append the latest Status Report (if requested or if significant changes occurred).
    - Format: `## Report [YYYY-MM-DD] - Health: [Color]`
- **`project_state.md`**: Update 'Execution Log' and 'Phases Status'.

### 2. Action Plan (The "Next Steps")
- **Directives**: Specific actions for the user/team (e.g., "Chase @Designer for Header").
- **Alerts**: "Risk R-02 is materializing due to Task T-10 delay."

Responsibilities (additional guardrails):
- Verify that an approval entry exists in `decision-log.md` for any `workplan-and-estimate.md` before marking Cutover/Production tasks as `in_progress`.
- If no approval is present within 48 hours of the approval request, automatically escalate to the Sponsor and record the escalation in `task-log.md` and `decision-log.md`.



## Example Scenarios

### Scenario A: Daily Standup Update
**Input**: `latest_updates` = "Frontend finished the login page. Backend is still stuck on AWS permissions."
**Action**:
-   Update `task-log.md`:
    -   Task "Frontend Login": Status -> **Done**.
    -   Task "Backend Setup": Status -> **Blocked** (Blocker: AWS Permissions).
-   Output: "Backend is blocked. Recommendation: Escalate to DevOps immediately."

### Scenario B: Weekly Status Report
**Input**: Request = "Generate Weekly Report"
**Action**:
-   Analyze `task-log.md`: 5/10 tasks done. 2 Blocked. Planning deadline was yesterday.
-   Health: **Yellow** (Slippage).
-   Update `status-reports.md`: Add new entry with Health Yellow and key blockers.
```