Periodic Project Update

Produces a stakeholder-ready status report by pulling real work out of this workspace's repos — never invent or guess milestones. If there isn't enough evidence for a line, leave it out (or ask the user). This skill is project-agnostic: it derives the project name, ticket-key prefix, and repo list fresh from whatever workspace it's run in.

When to Use

• Asked for a periodic (monthly, sprint, custom-range) project update, status report, or "what did we complete in <month>" summary.
• Trigger words: "project update", "monthly summary", "status report", "sprint recap", "key milestones", "what did we ship".

Inputs