Catalogue › Programme Management

CopilotForge - Programme Management

Use it in Copilot Cowork: download the Programme Management plugin for Copilot Cowork and upload it under Customize > Plugins > Upload plugin. How to install.

Mobilise and govern a coherent adoption, delivery or transformation programme.

Layer: transformation
Lead role: AI Programme Manager
Plugin name: copilotforge-programme-management

Skill Status Lifecycle Description

budget-and-capacity draft Mobilise, Deliver, Measure, Scale Plans and tracks an AI programme's budget and people capacity - services, internal time, licences as advised, and consumption costs such as Copilot Studio and Foundry usage - with forecasts, variance against tolerance, and monthly capacity of scarce roles such as knowledge owners and reviewers. Use when a programme needs a cost and capacity baseline, when consumption costs are growing, or when the same people are committed twice.

dependency-management draft Mobilise, Enable, Deliver, Launch, Improve Manages the dependencies an AI programme relies on - between workstreams, on platform and tenant changes, on suppliers and partners, on other programmes and on Microsoft releases and retirements - each with a giver, receiver, need-by date, status and fallback, watched through a release watch. Use when milestones wait on others, when a Microsoft change could move the plan, or when a partner or IT team must deliver something first.

integrated-roadmap draft Mobilise, Enable, Deliver, Launch Integrates every AI programme workstream plan - adoption, Champions, learning, knowledge, platform, agent delivery, governance and value - into one dated delivery plan with milestones, a critical path, cross-workstream dependencies and a baseline that changes only by decision. Use when workstreams plan separately, when nobody can say what the next milestone depends on, or when the strategic roadmap needs turning into a plan people can run.

programme-board-cadence draft Mobilise, Deliver, Measure Sets the governance rhythm of an AI programme - programme board, workstream leads meeting, design and change forum and sponsor checkpoints - with terms of reference, reporting flow, paper deadlines and a programme decision log, aligned with the CoE's forums rather than duplicating them. Use when a chartered programme needs its meetings set up, when the board has become a status briefing, or when programme decisions cannot be traced.

programme-charter draft Mobilise Charters an AI adoption, delivery or transformation programme - mandate, the outcomes it serves, scope and exclusions, workstreams, governance and decision rights, tolerances, funding envelope, roles and closure criteria - so the sponsor signs one agreed basis for running it. Use when an agreed pack or roadmap needs mobilising, when AI initiatives run without a common mandate, or when a sponsor asks what the programme is committing to.

programme-health draft Deliver, Assure, Launch, Measure, Scale, Improve Assesses and reports AI programme health across outcomes, schedule, cost, capacity, risk, adoption, assurance, governance and stakeholder confidence, with defined RAG criteria, an evidence-based narrative, corrective actions with owners, and a recovery plan when health is red. Use when the board needs a monthly health report, when status reports are all green but the programme feels stuck, or when a programme needs a health check or recovery.

programme-risk-log draft Mobilise, Enable, Deliver, Assure, Launch, Measure Runs the risks, assumptions, issues and decisions log for an AI programme, with AI-specific risk prompts, consistent scoring, owners by role, responses, review dates and escalation to the board, kept separate from solution risk tiers. Use when a programme is mobilising, when risks are known but owned by nobody, when assumptions about licences, knowledge or reviewers go unchecked, or when the board cannot see what threatens delivery.

stage-gates draft Mobilise, Enable, Deliver, Assure, Launch, Measure, Scale Defines the stage gates of an AI programme along the CopilotForge lifecycle - from mobilisation through enablement, delivery, launch and scale to closure - with the evidence each gate needs, who signs it off, how reviewer findings carry into it, and the outcomes go, conditional go, hold or stop. Use when a programme needs control points, when gates have become ceremonies, or when a sponsor asks what must be true before the next stage.

stakeholder-governance draft Mobilise, Deliver, Assure, Launch Governs how stakeholders take part in an AI programme's decisions - decision rights by decision type, who must be consulted or must approve (security, data protection, legal, HR, employee representatives, business units), escalation routes and time limits, and an engagement plan for governance stakeholders. Use when nobody knows who can approve a change, when decisions stall between functions, or when a required voice was left out.

supplier-management draft Mobilise, Enable, Deliver, Scale Selects and manages the partners and suppliers an AI programme relies on - deciding what to source, setting outcome-based requirements and criteria, testing Microsoft AI capability claims on evidence, structuring work packages, knowledge transfer and exit, and reviewing delivery at service level. Use when a programme needs a Microsoft partner or ISV, when a supplier underdelivers, or when the organisation risks depending on a partner for good.

Skill	Status	Lifecycle	Description
`budget-and-capacity`	draft	Mobilise, Deliver, Measure, Scale	Plans and tracks an AI programme's budget and people capacity - services, internal time, licences as advised, and consumption costs such as Copilot Studio and Foundry usage - with forecasts, variance against tolerance, and monthly capacity of scarce roles such as knowledge owners and reviewers. Use when a programme needs a cost and capacity baseline, when consumption costs are growing, or when the same people are committed twice.
`dependency-management`	draft	Mobilise, Enable, Deliver, Launch, Improve	Manages the dependencies an AI programme relies on - between workstreams, on platform and tenant changes, on suppliers and partners, on other programmes and on Microsoft releases and retirements - each with a giver, receiver, need-by date, status and fallback, watched through a release watch. Use when milestones wait on others, when a Microsoft change could move the plan, or when a partner or IT team must deliver something first.
`integrated-roadmap`	draft	Mobilise, Enable, Deliver, Launch	Integrates every AI programme workstream plan - adoption, Champions, learning, knowledge, platform, agent delivery, governance and value - into one dated delivery plan with milestones, a critical path, cross-workstream dependencies and a baseline that changes only by decision. Use when workstreams plan separately, when nobody can say what the next milestone depends on, or when the strategic roadmap needs turning into a plan people can run.
`programme-board-cadence`	draft	Mobilise, Deliver, Measure	Sets the governance rhythm of an AI programme - programme board, workstream leads meeting, design and change forum and sponsor checkpoints - with terms of reference, reporting flow, paper deadlines and a programme decision log, aligned with the CoE's forums rather than duplicating them. Use when a chartered programme needs its meetings set up, when the board has become a status briefing, or when programme decisions cannot be traced.
`programme-charter`	draft	Mobilise	Charters an AI adoption, delivery or transformation programme - mandate, the outcomes it serves, scope and exclusions, workstreams, governance and decision rights, tolerances, funding envelope, roles and closure criteria - so the sponsor signs one agreed basis for running it. Use when an agreed pack or roadmap needs mobilising, when AI initiatives run without a common mandate, or when a sponsor asks what the programme is committing to.
`programme-health`	draft	Deliver, Assure, Launch, Measure, Scale, Improve	Assesses and reports AI programme health across outcomes, schedule, cost, capacity, risk, adoption, assurance, governance and stakeholder confidence, with defined RAG criteria, an evidence-based narrative, corrective actions with owners, and a recovery plan when health is red. Use when the board needs a monthly health report, when status reports are all green but the programme feels stuck, or when a programme needs a health check or recovery.
`programme-risk-log`	draft	Mobilise, Enable, Deliver, Assure, Launch, Measure	Runs the risks, assumptions, issues and decisions log for an AI programme, with AI-specific risk prompts, consistent scoring, owners by role, responses, review dates and escalation to the board, kept separate from solution risk tiers. Use when a programme is mobilising, when risks are known but owned by nobody, when assumptions about licences, knowledge or reviewers go unchecked, or when the board cannot see what threatens delivery.
`stage-gates`	draft	Mobilise, Enable, Deliver, Assure, Launch, Measure, Scale	Defines the stage gates of an AI programme along the CopilotForge lifecycle - from mobilisation through enablement, delivery, launch and scale to closure - with the evidence each gate needs, who signs it off, how reviewer findings carry into it, and the outcomes go, conditional go, hold or stop. Use when a programme needs control points, when gates have become ceremonies, or when a sponsor asks what must be true before the next stage.
`stakeholder-governance`	draft	Mobilise, Deliver, Assure, Launch	Governs how stakeholders take part in an AI programme's decisions - decision rights by decision type, who must be consulted or must approve (security, data protection, legal, HR, employee representatives, business units), escalation routes and time limits, and an engagement plan for governance stakeholders. Use when nobody knows who can approve a change, when decisions stall between functions, or when a required voice was left out.
`supplier-management`	draft	Mobilise, Enable, Deliver, Scale	Selects and manages the partners and suppliers an AI programme relies on - deciding what to source, setting outcome-based requirements and criteria, testing Microsoft AI capability claims on evidence, structuring work packages, knowledge transfer and exit, and reviewing delivery at service level. Use when a programme needs a Microsoft partner or ISV, when a supplier underdelivers, or when the organisation risks depending on a partner for good.

Credit

Created by Simon Foote as part of CopilotForge. Content is licensed under CC BY 4.0; keep the credit in each skill's license and authors fields when you share or adapt it. See NOTICE.md in the repository.