# Project Execution Management

> Coordinates ERP Project Execution Management implementation guidance and routes work to developer-created functional-area skills.

- Skill: `oracle/project-execution-management` (Agent Skill)
- Install (CLI): `npx get-skill add oracle/project-execution-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/project-execution-management/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/project-execution-management

---


# Project Execution Management

## Purpose

Coordinates ERP Project Execution Management implementation guidance across functional areas, setup tasks, and standard implementation activities.

## When to Use

Use this offering-level skill after Project Execution Management is in scope and before routing to a specific functional-area skill.

## Catalog Identity

- Pillar: `ERP`
- Pillar slug: `erp`
- Offering code: `PJT_PROJECT_EXECUTION_MGMT`
- Offering slug: `project-execution-management`
- Offering folder: `pillars/erp/project-execution-management`
- Offering mapping source: `knowledge/setup-task-catalog/release/pillars-offerings-mapping.json`
- Setup task catalog source: `knowledge/setup-task-catalog/release/offering-functional-area-task-catalog.json`

## Routing Responsibility

This skill routes control to functional-area skills created by developers under this folder. Developers should create functional-area skills with `core.fusion-dev.pillar-skill-gen` using the catalog-backed path pattern:

```text
pillars/erp/project-execution-management/{functional-area-slug}/
```

When a requested functional area is not yet present under this offering, use the setup catalog below to identify the matching functional area and invoke `core.fusion-dev.pillar-skill-gen` to generate the child skill before adding functional-area-specific guidance.

## Inputs

- `implementation_objective`
- `project_context`
- `erp_scope`
- `project_execution_management_requirements`

## Outputs

- `project_execution_management_scope`
- `functional_area_skill_plan`
- `project_execution_management_work_products`
- `token_usage_record`

## Functional Areas From Catalog

Source: `knowledge/setup-task-catalog/release/offering-functional-area-task-catalog.json`
Offering code: `PJT_PROJECT_EXECUTION_MGMT`
Functional area count: `3`
Setup task count: `86`

- `ORA_PJT_PROJECT_EXECUTION_FA`: Project Execution
- `PJT_PJR_DEPOLYED`: Project Resource Management
- `ORA_ASK_APPLICATION_EXTENSIONS`: Application Extensions

## Implementation Notes

- Keep offering-level planning, scope decisions, sequencing, and cross-functional-area handoffs in this skill.
- Put functional-area-specific implementation guidance in generated child skills under this offering folder.
- Use `core.fusion-dev.pillar-skill-gen` for child functional-area skill creation so generated skills follow the repository contract.
- Use `core.fusion-dev.fusionapps-resource-authoring` after child skill creation when Oracle FusionApps `ora-resource/` guidance is needed.
- Do not create setup-task-specific skills directly under this offering folder unless the user explicitly requests nested task-level skill generation through the pillar skill generator.

