# Prince2 Stage Control Pack

> Run PRINCE2 Controlling a Stage: work package tracking, highlight reports, risk and issue control, tolerance checks, change handling, and corrective action planning.

- Skill: `danielpradilla/prince2-stage-control-pack` (Agent Skill)
- Install (CLI): `npx skillmds add danielpradilla/prince2-stage-control-pack`
- Raw SKILL.md: https://api.skillmd.com/api/skills/danielpradilla/prince2-stage-control-pack/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: danielpradilla (https://skillmd.com/u/danielpradilla)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/danielpradilla/prince2-stage-control-pack

---


# PRINCE2 Stage Control Pack

For detailed management product definitions, read `../../references/prince2-management-products.md` when the user needs a complete PRINCE2 document set or asks what each artifact is for.

Use this workflow during an active delivery stage when the project manager needs to control progress and keep the project within tolerance.

## Inputs To Ask For

- Current stage plan
- Active work packages
- Latest checkpoints
- Risks, issues, changes, and dependencies
- Tolerances for time, cost, quality, scope, benefits, risk, and sustainability
- Decisions or escalations needed

## Output Structure

### 1. Stage Control Snapshot
- Stage objective
- Current status
- Tolerance position
- Confidence level
- Immediate management action

### 2. Work Package Control
- Work package
- Owner or team manager
- Status
- Products due
- Quality checks due
- Risks or blockers
- Action needed

### 3. Highlight Report
- Period covered
- Progress this period
- Planned next period
- Current and forecast tolerance position
- Risks and issues
- Decisions required

### 4. Risk, Issue, And Change Updates
- New entries
- Updated impact
- Owner
- Response
- Escalation threshold
- Link to affected plan or product

### 5. Corrective Actions
- Action
- Owner
- Due date
- Expected effect
- Follow-up point

## Quality Bar

- Distinguish normal variance from a tolerance threat.
- Escalate exceptions early.
- Keep work package tracking tied to product delivery and quality criteria.
- Update logs and registers as part of the output, not as an afterthought.