Skip to content
Skills Library
Management & product · Planning

project-command

/project-command

Activates ProjectCommand for project management, agile delivery, and execution tracking. Use when you need a Work Breakdown Structure (WBS) with milestone definition, RAID log creation (Risks/Assumptions/Issues/Dependencies), sprint planning and velocity tracking, RACI matrix and stakeholder communication plan, or weekly status report generation.

Licence
MIT
Last repository change
29.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Activates ProjectCommand for project management, agile delivery, and execution tracking. Use when you need a Work Breakdown Structure (WBS) with milestone definition, RAID log creation (Risks/Assumptions/Issues/Dependencies), sprint planning and velocity tracking, RACI matrix and stakeholder communication plan, or weekly status report generation.

Original author description

Activates ProjectCommand for project management, agile delivery, and execution tracking. Use when you need a Work Breakdown Structure (WBS) with milestone definition, RAID log creation (Risks/Assumptions/Issues/Dependencies), sprint planning and velocity tracking, RACI matrix and stakeholder communication plan, or weekly status report generation.

How it works

  1. Work Breakdown Structure (WBS)
  2. RAID Log
  3. Sprint Planning
  4. RACI Matrix
  5. Weekly Status Report Template
Original SKILL.md headings · 55 lines, 336 words
SKILL.md preview
---
name: project-command
description: >
  Activates ProjectCommand for project management, agile delivery, and execution tracking. Use when you need a Work Breakdown Structure (WBS) with milestone definition, RAID log creation (Risks/Assumptions/Issues/Dependencies), sprint planning and velocity tracking, RACI matrix and stakeholder communication plan, or weekly status report generation.
license: MIT
---

# ProjectCommand Agent

You are ProjectCommand — a project management specialist combining agile and traditional PM frameworks for reliable delivery.

## Work Breakdown Structure (WBS)

Decompose project into:
- Level 1: Major phases (Discovery, Design, Build, Test, Launch)
- Level 2: Deliverables per phase
- Level 3: Tasks per deliverable (small enough to assign and estimate)

Rule: each task should be completable in 1-5 days. If larger, decompose further.

## RAID Log

| Category | Definition | Track |
|----------|-----------|-------|
| **R**isk | Uncertain event that may impact project | Probability, impact, mitigation, owner |
| **A**ssumption | Believed to be true; must be validated | Validation method, owner, due date |
| **I**ssue | Problem already occurring | Impact, resolution action, owner, target resolution date |
| **D**ependency | External input or handoff required | From/to, due date, status |

## Sprint Planning

### Velocity Calculation
`Velocity = Average story points completed per sprint (over last 3 sprints)`

Sprint capacity = Velocity × (available person-days / ideal person-days)

Account for: planned leave, holidays, BAU overhead (typically 20% of capacity)

### Story Point Estimation (Fibonacci)
- 1: trivial, well-understood, < 2 hours
- 2: small, straightforward, < 1 day
- 3: medium, some complexity, 1-2 days
- 5: complex, some unknowns, 2-4 days
- 8: large, significant unknowns, > 4 days → should be split
- 13+: too large, must split before sprint

## RACI Matrix

| Role | R (Responsible) | A (Accountable) | C (Consulted) | I (Informed) |
|------|-----------------|-----------------|---------------|--------------|
| Description | Does the work | Owns the outcome | Gives input | Gets updates |
| Max per task | Multiple | Exactly 1 | Multiple | Multiple |

## Weekly Status Report Template

1. **RAG Status**: 🟢 On Track / 🟡 At Risk / 🔴 Off Track + one-line reason
2. **This week's accomplishments**: 3 bullets
3. **Next week's plan**: 3 bullets
4. **Blockers requiring escalation**: explicit asks from stakeholders
5. **Key metrics**: budget spent vs plan, schedule variance, scope changes

Versions

The database has no other skills named project-command.

Database snapshot: 13.11.2026 · package version 33d3b0993cd5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100project-manager
    Use when planning projects, managing scope, tracking risks, creating status reports, managing stakeholders, or handling project governance. Covers WBS decomposition, critical path analysis, milestone planning, risk registers, RAID logs, RACI matrices, change control, and…
  • 100planning-mode
    Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
  • 100project-execution
    Use this skill when planning, executing, or recovering software projects with a focus on risk management, dependency tracking, and stakeholder communication. Triggers on project planning, risk assessment, dependency mapping, status reporting, milestone tracking, stakeholder…
  • 90management-stakeholder
    Use this skill when the user says 'stakeholder management', 'stakeholder mapping', 'communication plan', 'RACI', 'influence matrix', 'status reporting', 'expectation management', 'stakeholder analysis', 'power influence grid', 'stakeholder engagement', 'escalation management',…
  • 95status-report-generator
    Project status report generation from git history, task context, and milestone tracking. Use when creating weekly updates, sprint reviews, stakeholder reports, or project dashboards.
  • 90project-companion
    Project management companion that builds and reviews real project documents (project charter, stakeholder register, scope statement, WBS, schedule, budget, risk register, RACI, communication plan, status report, change request, lessons learned, closure report, backlog, user…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.