# Project Context

**Project:** [Project Name]
**PM:** [Your Name]
**Phase:** [Planning / Execution / Closeout]
**Key stakeholders:** [Sponsor name], [Client name], [Tech lead name]
**Deadline:** [Target completion date]

## Communication Style

* Write status updates in outcomes, not activity ("Testing is complete" not "The team has been testing")
* Use plain language — no jargon unless the audience is technical
* Default to bullet points over paragraphs for anything action-oriented
* When summarizing a meeting or thread, lead with decisions made, then actions, then context
* Escalation tone: matter-of-fact, not alarmist

## Document Conventions

* Date format: YYYY-MM-DD
* Status labels: `On Track` / `At Risk` / `Delayed` / `Complete`
* RAG ratings: Red = blocked or missed, Amber = at risk with a plan, Green = on track
* File naming: `YYYY-MM-DD_DocumentType_Version` (e.g., `2025-08-06_StatusReport_v2`)
* Owner field always uses full name, never initials

## Recurring Document Types

### Status Report
Structure: Executive Summary → Milestones → Risks & Issues → Decisions Needed → Next Steps
Length: Fits on one page. Cut anything that does not require stakeholder awareness.

### Meeting Notes
Structure: Date / Attendees / Decisions / Actions (owner + due date) / Parking Lot
Do not summarize discussion — only record what was decided or assigned.

### Risk Log Entry
Fields: Risk ID, Description, Likelihood (H/M/L), Impact (H/M/L), Mitigation, Owner, Status

### Action Item
Format: `[Owner] will [verb + specific outcome] by [date]`
Never write an action without an owner and a due date.

## Project-Specific Rules

* This project uses [methodology: Agile / Waterfall / Hybrid]
* Sprint/reporting cadence: [weekly / bi-weekly]
* Budget is tracked in [tool name] — do not include raw numbers in documents shared externally
* Decisions require sign-off from [name/role] before they are final
* [Any recurring naming convention, process rule, or constraint specific to this project]

## What Goes in Chat, Not Here

One-off analysis, draft language for a single email, or context that only applies to today's task — keep those in the session, not in this file.