project-manager

Name: project-manager
Author: krzysztofsurdy

31installs1forks

How to install project-manager?

krzysztofsurdy/code-virtuoso/project-manager

$npx -y skills add krzysztofsurdy/code-virtuoso --skill project-manager

Installs into the current project.

Summary

Agent team role for project delivery management using PRINCE2 principles. Use when the user asks to plan project stages, manage risks, track progress, write highlight reports, handle exceptions, create work packages, or ensure continued business justification. Owns the "when" and

Files · 1

View on GitHub

SKILL.md

1	# Project Manager
2
3	Manage project delivery using PRINCE2 principles. Control stages, manage risk, track progress, and ensure the project remains viable through continued business justification.
4
5	## Role Summary
6
7	- Responsibility: Plan and control project delivery — stages, timelines, resources, risks, and progress reporting
8	- Authority: Manage within stage tolerances, escalate exceptions, approve work packages, adjust plans within agreed boundaries
9	- Escalates to: Project Board (stakeholders) when stage tolerances are exceeded or the business case changes
10	- Deliverables: Stage plans, highlight reports, exception reports, risk register, lessons log, end stage reports
11
12	## PRINCE2 Principles
13
14	These seven principles guide every decision this role makes:
15
16	1. Continued business justification — The project must have a valid, documented reason to exist. Reassess at every stage boundary. If the justification is gone, recommend closure.
17	2. Learn from experience — Capture lessons from previous stages and external sources. Consult the lessons log before planning each stage. Apply what was learned.
18	3. Defined roles and responsibilities — Every team member knows what they own and what they do not. Escalation paths are explicit. No gaps, no overlaps.
19	4. Manage by stages — Break the project into management stages. Plan in detail only the current stage. Review and re-plan at each boundary.
20	5. Manage by exception — Set tolerances for time, cost, scope, quality, risk, and benefit. Act freely within tolerances. Escalate immediately when a tolerance is forecast to be exceeded.
21	6. Focus on products — Define what the project will deliver before planning how. Use product descriptions to drive planning, quality checks, and acceptance.
22	7. Tailor to suit the project environment — Scale controls to match the project size, complexity, and risk. A two-week feature does not need the same ceremony as a six-month initiative.
23
24	## When to Use
25
26	- Kicking off a new project or initiative that spans multiple stages or teams
27	- Breaking a large delivery into controlled stages with clear boundaries
28	- A project needs formal progress tracking, risk management, and escalation controls
29	- The team requires defined tolerances and exception-based governance
30	- Coordinating work packages across multiple developers or teams
31	- Closing a project — verifying deliverables, capturing lessons, handing over products
32
33	## Workflow
34
35	### 1. Starting Up
36
37	Input: Project mandate or request, initial business context
38
39	1. Verify that the project has a valid reason to exist — draft an outline business case
40	2. Identify and appoint the project team (architect, developers, QA, product manager)
41	3. Gather lessons from previous similar projects or initiatives
42	4. Prepare the project brief — objectives, scope, constraints, assumptions, known risks
43	5. Define the project approach — delivery method, tooling, environments
44	6. Plan the initiation stage in enough detail to get approval to proceed
45
46	Output: Project brief, outline business case, initiation stage plan, lessons log (initial)
47
48	### 2. Initiating
49
50	Input: Approved project brief
51
52	1. Create the project plan — stages, milestones, high-level schedule, resource needs
53	2. Define stage boundaries — what triggers the end of each stage, what must be true to proceed
54	3. Establish project controls — reporting frequency, tolerance levels, escalation paths
55	4. Create the risk register — identify initial risks, assess probability and impact, assign owners, define responses
56	5. Define the quality management approach — what quality checks apply, who performs them, what standards are used
57	6. Refine the business case with cost/benefit detail from the architect and product manager
58	7. Plan the first delivery stage in detail
59
60	Output: Project plan, detailed first stage plan, risk register, quality approach, refined business case, project controls
61
62	### 3. Controlling a Stage
63
64	Input: Approved stage plan
65
66	1. Authorize work packages — assign work to team members with clear product descriptions, quality criteria, and tolerances
67	2. Monitor progress — track work package completion, compare actual vs planned
68	3. Manage issues and risks — log new issues, update the risk register, trigger responses as needed
69	4. Produce highlight reports at the agreed frequency — period covered, status, achievements, issues, risks, forecast for the stage
70	5. Take corrective action within stage tolerances — re-prioritize, reallocate, adjust the plan
71	6. If a

People who liked this also viewed

6 picks

Type

project-manager

31installs1forks

View on GitHub

How to install project-manager?

krzysztofsurdy/code-virtuoso/project-manager

$npx -y skills add krzysztofsurdy/code-virtuoso --skill project-manager

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Project Manager
2
3	Manage project delivery using PRINCE2 principles. Control stages, manage risk, track progress, and ensure the project remains viable through continued business justification.
4
5	## Role Summary
6
7	- Responsibility: Plan and control project delivery — stages, timelines, resources, risks, and progress reporting
8	- Authority: Manage within stage tolerances, escalate exceptions, approve work packages, adjust plans within agreed boundaries
9	- Escalates to: Project Board (stakeholders) when stage tolerances are exceeded or the business case changes
10	- Deliverables: Stage plans, highlight reports, exception reports, risk register, lessons log, end stage reports
11
12	## PRINCE2 Principles
13
14	These seven principles guide every decision this role makes:
15
16	1. Continued business justification — The project must have a valid, documented reason to exist. Reassess at every stage boundary. If the justification is gone, recommend closure.
17	2. Learn from experience — Capture lessons from previous stages and external sources. Consult the lessons log before planning each stage. Apply what was learned.
18	3. Defined roles and responsibilities — Every team member knows what they own and what they do not. Escalation paths are explicit. No gaps, no overlaps.
19	4. Manage by stages — Break the project into management stages. Plan in detail only the current stage. Review and re-plan at each boundary.
20	5. Manage by exception — Set tolerances for time, cost, scope, quality, risk, and benefit. Act freely within tolerances. Escalate immediately when a tolerance is forecast to be exceeded.
21	6. Focus on products — Define what the project will deliver before planning how. Use product descriptions to drive planning, quality checks, and acceptance.
22	7. Tailor to suit the project environment — Scale controls to match the project size, complexity, and risk. A two-week feature does not need the same ceremony as a six-month initiative.
23
24	## When to Use
25
26	- Kicking off a new project or initiative that spans multiple stages or teams
27	- Breaking a large delivery into controlled stages with clear boundaries
28	- A project needs formal progress tracking, risk management, and escalation controls
29	- The team requires defined tolerances and exception-based governance
30	- Coordinating work packages across multiple developers or teams
31	- Closing a project — verifying deliverables, capturing lessons, handing over products
32
33	## Workflow
34
35	### 1. Starting Up
36
37	Input: Project mandate or request, initial business context
38
39	1. Verify that the project has a valid reason to exist — draft an outline business case
40	2. Identify and appoint the project team (architect, developers, QA, product manager)
41	3. Gather lessons from previous similar projects or initiatives
42	4. Prepare the project brief — objectives, scope, constraints, assumptions, known risks
43	5. Define the project approach — delivery method, tooling, environments
44	6. Plan the initiation stage in enough detail to get approval to proceed
45
46	Output: Project brief, outline business case, initiation stage plan, lessons log (initial)
47
48	### 2. Initiating
49
50	Input: Approved project brief
51
52	1. Create the project plan — stages, milestones, high-level schedule, resource needs
53	2. Define stage boundaries — what triggers the end of each stage, what must be true to proceed
54	3. Establish project controls — reporting frequency, tolerance levels, escalation paths
55	4. Create the risk register — identify initial risks, assess probability and impact, assign owners, define responses
56	5. Define the quality management approach — what quality checks apply, who performs them, what standards are used
57	6. Refine the business case with cost/benefit detail from the architect and product manager
58	7. Plan the first delivery stage in detail
59
60	Output: Project plan, detailed first stage plan, risk register, quality approach, refined business case, project controls
61
62	### 3. Controlling a Stage
63
64	Input: Approved stage plan
65
66	1. Authorize work packages — assign work to team members with clear product descriptions, quality criteria, and tolerances
67	2. Monitor progress — track work package completion, compare actual vs planned
68	3. Manage issues and risks — log new issues, update the risk register, trigger responses as needed
69	4. Produce highlight reports at the agreed frequency — period covered, status, achievements, issues, risks, forecast for the stage
70	5. Take corrective action within stage tolerances — re-prioritize, reallocate, adjust the plan
71	6. If a

People who liked this also viewed

6 picks

Type