{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "project-status",
  "name": "Project status",
  "category": "Work",
  "summary": "Turn a project update into current progress, variance, and decisions needed.",
  "use_cases": [
    "Milestone updates",
    "Delivery tracking",
    "Stakeholder status reports"
  ],
  "word_count": 149,
  "url": "https://sho.rten.it/methods/project-status/",
  "instructions_url": "https://sho.rten.it/methods/project-status/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/project-status/SKILL.md",
  "json_url": "https://sho.rten.it/methods/project-status/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/project-status/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#project-status",
  "skill_name": "project-status",
  "skill_description": "Turn a project update into current progress, variance, and decisions needed. Use for Milestone updates, Delivery tracking, Stakeholder status reports.",
  "agents_md_url": "https://sho.rten.it/methods/project-status/AGENTS.md",
  "sources": [],
  "instructions": "Condense the supplied project update into a snapshot of delivery status. Use this for progress against an agreed plan, not a weekly activity log.\n\nState the goal or milestone and the reporting date. Separate completed work from work in progress. Keep the baseline date, latest forecast, and reason for any stated variance. A forecast is not a commitment, and work started is not work finished. Keep the source's confidence level; do not invent a traffic-light rating.\n\nRetain blockers, dependencies, scope changes, and decisions that could change delivery. Pair each requested action with its named owner and due date when supplied. Distinguish a request awaiting approval from approved work.\n\nUse compact sections: Status, Change from plan, and Needed next. Prefer outcomes over lists of meetings. Remove activity detail only when it does not explain progress or delay. State an unknown forecast as unknown rather than assuming the baseline still holds.",
  "example": {
    "before": "This is the 6 May status update for the archive migration, whose goal is to move the support archive into the new search service. The original completion date was 10 May. The team has finished migrating the 2023 and 2024 records. Migration of the 2025 records is in progress and has not passed validation. The current completion forecast is 14 May, assuming infrastructure gives us the extra storage by 8 May. This is a forecast, not an approved change to the committed date. The forecast moved because the first data import exceeded the planned storage allocation. Sam has asked infrastructure lead Jo to confirm the storage by 8 May. Sam also proposed moving attachments into a later phase, but that scope change has not been approved. The team held three migration syncs this week.",
    "after": "Status — 6 May: Move the support archive to the new search service. 2023–2024 records are migrated. The 2025 migration is in progress and has not passed validation.\n\nChange from plan: Baseline completion is 10 May. Forecast is 14 May if extra storage arrives by 8 May; the committed date has not changed. The first import exceeded planned storage.\n\nNeeded next: Sam asked Jo to confirm storage by 8 May. Sam's proposal to defer attachments remains unapproved.",
    "context": "Archive migration status",
    "must_preserve": [
      "6 May report and migration goal",
      "2023–2024 completed; 2025 in progress and not validated",
      "10 May baseline; 14 May conditional forecast, no approved date change",
      "Storage exceeded allocation; required by 8 May",
      "Sam requested confirmation from Jo by 8 May",
      "Attachment deferral unapproved"
    ],
    "omitted": [
      "Three routine migration syncs"
    ],
    "kind": "illustrative"
  }
}