Resource Allocation Skill

Systematic resource planning across portfolio for optimal utilization.

Purpose

This skill provides a framework for:

• Capacity planning across projects
• Resource conflict identification
• Skills gap analysis
• Allocation optimization
• Utilization monitoring

Prerequisites

Before resource allocation, ensure:

Resource Allocation Gates

Gate 1: Resource Inventory

Objective: Establish baseline of available resources

Actions:

1. List all available resources (people, teams)
2. Document skills per resource
3. Capture availability (FTE, dates)
4. Note constraints (PTO, training, etc.)

Output: docs/pmo/{date}/resource-inventory.md

Inventory Template:

Gate 2: Demand Analysis

Objective: Understand resource demand across portfolio

Actions:

1. Collect resource requests from projects
2. Categorize by role/skill
3. Map to timeline
4. Aggregate total demand

Demand Template:

Output: docs/pmo/{date}/resource-demand.md

Gate 3: Gap Analysis

Objective: Identify mismatches between supply and demand

Actions:

1. Compare inventory to demand
2. Identify capacity gaps (over/under)
3. Identify skill gaps
4. Document timeline conflicts

Gap Types:

Output: docs/pmo/{date}/resource-gaps.md

Gate 4: Conflict Resolution

Objective: Resolve resource conflicts across projects

Actions:

1. List all conflicts
2. Analyze priority-based resolution
3. Propose alternatives (hire, defer, redistribute)
4. Document trade-offs

Resolution Options:

Output: docs/pmo/{date}/conflict-resolution.md

Gate 5: Allocation Plan

Objective: Create optimal resource allocation plan

Actions:

1. Assign resources to projects
2. Document allocation percentages
3. Define handoff points
4. Create monitoring plan

Allocation Template:

Utilization Target: 70-85% (leaves buffer for issues)

Output: docs/pmo/{date}/allocation-plan.md

Anti-Rationalization Table

See shared-patterns/anti-rationalization.md for universal anti-rationalizations.

Resource-Specific Anti-Rationalizations

Pressure Resistance

See shared-patterns/pressure-resistance.md for universal pressure scenarios.

Resource-Specific Pressures

Blocker Criteria - STOP and Report

ALWAYS pause and report blocker for:

Cannot Be Overridden

The following requirements are NON-NEGOTIABLE:

If user insists on violating these:

1. Escalate to orchestrator
2. Do NOT proceed with unrealistic allocation
3. Document the request and your refusal

Severity Calibration

When reporting resource issues:

Report ALL severities. Escalate CRITICAL immediately. Address HIGH this week.

Output Format

Resource Allocation Summary

# Resource Allocation Summary - [Date]

## Capacity Overview

| Metric | Value | Status |
|--------|-------|--------|
| Total FTE Available | X | - |
| Total FTE Demanded | X | - |
| Utilization Rate | X% | Green/Yellow/Red |
| Open Positions | N | - |

## Allocation by Project

| Project | FTE Allocated | Utilization | Status |
|---------|--------------|-------------|--------|
| [Project] | X | X% | Green/Yellow/Red |

## Gaps Identified

| Gap Type | Description | Impact | Resolution |
|----------|-------------|--------|------------|
| [Type] | [Description] | [Impact] | [Proposed] |

## Conflicts

| Conflict | Projects | Resource | Proposed Resolution |
|----------|----------|----------|---------------------|
| [ID] | [Projects] | [Resource] | [Resolution] |

## Recommendations

1. [Recommendation with rationale]
2. [Recommendation with rationale]

## Decisions Required

1. [Decision needed with options]

Execution Report

Base metrics per shared-patterns/execution-report.md:

Resource-Specific Details

When Resource Allocation Is Not Needed

MUST: Full resource allocation REQUIRED for the following conditions:

MUST: When in doubt, refresh the allocation plan. Stale resource data causes delivery failures.