Programme steering packs
Turn a folder of weekly notes into a delivery-health chart and a digest a sponsor will actually read.
— Operations & Process
Project status digest
Reads a set of weekly status notes for progress, blockers and RAG, charts the trend, and writes an executive digest focused on trajectory.
- Operations & Process
- Traceable reasoning
- Runs anywhere
half a day → ~10 minutes
For a typical multi-document review workflow
No coding required
- Input
- A set of weekly or fortnightly status notes
- Output
- An exec-ready digest of trajectory, risks and this week's attention list
- Runs in
- Skillsize · ChatGPT · Claude · Copilot
- Export
- SKILL.md · MCP
- Time saved
- ~half a day per run
— USE CASES
What people use Project status digest for
Portfolio roll-up
Compare trajectory across workstreams where each lead writes their update in a different style.
Escalation spotting
Surface blockers that have persisted across several weeks rather than the ones raised loudest this week.
What it works from
- A set of weekly or fortnightly status notes
- Your RAG definitions
- The reporting period and audience
What you get back
- An exec-ready digest of trajectory, risks and this week's attention list
- A week-by-week delivery-health chart
- Per-note extraction of progress, blockers and RAG
— HOW IT BEHAVES
How Project status digest produces its result
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Whole document sets at once
A folder of material is processed as one set, so cross-document patterns surface instead of being read one file at a time.
Charted, not just stated
The pattern is visualised from the computed data, so the trend is legible at a glance.
Composed as work product
Findings are written up as a document that reads like professional output rather than raw model text.
Enriched row by row
Each row gains derived columns from the analysis, keeping the source data and the judgement side by side.
Why this is expensive by hand
Weekly status notes accumulate, and nobody reads them in aggregate. Programme steering packs is the typical trigger — turn a folder of weekly notes into a delivery-health chart and a digest a sponsor will actually read. Done properly it is defensible; done at pace it becomes a judgement call nobody can retrace. And "properly" usually means half a day of manual work.
How this Skill produces it
Skillsize turns that work into a Skill: you supply the material, and what comes back is an exec-ready digest of trajectory, risks and this week's attention list, with a week-by-week delivery-health chart. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. In effect, half a day of senior time compresses into ~10 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.
Who it's for
- Independent consultants codifying their own methodology
- Strategy and transformation teams standardising delivery
- Internal advisory functions under pressure to produce faster
- Operators who need defensible output, not a one-off chat answer
Run it in Skillsize — or export it anywhere
Project status digest exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
ChatGPTClaudeCopilotAI Products (MCP)
More Operations & Process Skills
Browse the full library →Operations & Process
Automation opportunity map
Maps team or function activities to automation potential, computing addressable effort and bucketing opportunities into a prioritised roadmap.
Operations & Process
Control failure → incident RCA pattern engine
Joins control test results to incident logs by process to show where control failures are actually producing incidents, grouped by systemic weakness with residual risk quantified.
Operations & Process
Process diagnostic
Inventories every process step with its owner, system, effort and wait time, tests each against bottleneck, duplication, handoff and control-gap lenses, and returns a prioritised 30/60/90 improvement backlog.