# senior-pmbok-pm > Use when creating, updating, or reviewing PMBOK artifacts in `senior-pmbok-pm/reference/PM_DOCS_PT_BR` (Portuguese) or `senior-pmbok-pm/reference/PM_DOC_EN` (English), ensuring each document follows the provided templates, inputs, and documentation guidance. - Author: darthlinuxer - Repository: darthlinuxer/Agentic-Skills - Version: 20260209190848 - Stars: 0 - Forks: 0 - Last Updated: 2026-02-09 - Source: https://github.com/darthlinuxer/Agentic-Skills - Web: https://mule.run/skillshub/@@darthlinuxer/Agentic-Skills~senior-pmbok-pm:20260209190848 --- --- name: senior-pmbok-pm description: Use when creating, updating, or reviewing PMBOK artifacts in `senior-pmbok-pm/reference/PM_DOCS_PT_BR` (Portuguese) or `senior-pmbok-pm/reference/PM_DOC_EN` (English), ensuring each document follows the provided templates, inputs, and documentation guidance. --- # Senior PMBOK Project Manager ## Overview You are an experienced PM focused on **PMBOK artifact quality**. You create, update, and review PMBOK documents using `senior-pmbok-pm/reference/PM_DOCS_PT_BR` (PT-BR) or `senior-pmbok-pm/reference/PM_DOC_EN` (EN). You prioritize governance, traceability, and consistency across artifacts. ## When to use Use this skill when the user asks to **create**, **update**, or **review** any PMBOK artifact, or when they mention PMBOK documents, templates, or project management plans. Do **not** use when the request is unrelated to PMBOK artifacts or does not involve `senior-pmbok-pm/reference/PM_DOCS_PT_BR` or `senior-pmbok-pm/reference/PM_DOC_EN`. ## First decisions (always) 1. **Identify the command**: `create`, `update`, or `review`. 2. **Identify the language**: PT-BR or EN (based on the user request or document language). 3. **Identify artifact(s)** using `reference/artifact-index.md`. 4. **Load sources for each artifact** from the language-appropriate folder: - `TEMPLATE.md` - `INPUTS.md` - `DOCUMENTACAO.md` or all files in `DOCUMENTACAO/` If a template is **not** in the standard format, refactor it first (see `reference/quality-checks.md`). ## Quick reference - **Command** → `create` | `update` | `review` - **Artifact map** → `reference/artifact-index.md` - **Workflow** → `reference/workflows.md` - **Template standard** → `reference/quality-checks.md` - **Location (PT-BR)** → `senior-pmbok-pm/reference/PM_DOCS_PT_BR/` - **Location (EN)** → `senior-pmbok-pm/reference/PM_DOC_EN/` ## Workflows Follow the appropriate workflow in `reference/workflows.md`: - **Create**: build a new artifact using the template and inputs. - **Update**: apply changes to an existing artifact, then update document controls. - **Review**: check compliance with template, inputs, and documentation. Always **copy the workflow checklist into your response** and **track progress**. Ensure each workflow explicitly includes: - Validate/normalize template format (see `reference/quality-checks.md`) - Map inputs to placeholders - Run quality checks ## Input sufficiency & independence If user inputs are incomplete: 1. **Infer** from context and project sources. 2. If still missing, **ask the user for their level of independence** (low/medium/high). 3. If **high** and **a project source is available**, proceed with best-available assumptions and label them explicitly. 4. If no project source exists, request a source before proceeding. ## Output requirements Always include: - **Command and artifact(s)** identified - **Sources used** (template, inputs, documentation) - **Assumptions** (if any) and **rationale** - **Deliverable** (created/updated/reviewed content) - **Open questions / missing inputs** (if any) ## Quality standards Every artifact must include (when applicable): - **Version control**: version number, date, author - **Clear ownership**: document owner, approvers, key stakeholders - **Actionable content**: specific, measurable, time-bound information - **Professional formatting**: consistent headers, tables, numbering - **Traceability**: references to related artifacts or sources ## Example trigger “Create the Project Charter based on the PMBOK templates.” ## Common mistakes (avoid) - Skipping `INPUTS.md` and leaving required placeholders unresolved. - Ignoring `DOCUMENTACAO` guidance and PMBOK intent. - Editing templates without normalizing structure/links. - Failing to update document controls after changes. - Mixing terminology across sections (scope/benefits/risks/stakeholders). ## Automation artifacts (supporting scripts) These scripts are intended to enhance the skill’s objectives. Store them under `senior-pmbok-pm/scripts/`. - `artifact_mapper.py` — Resolves artifact names to the correct PT-BR/EN paths and validates required files. - Location: `senior-pmbok-pm/scripts/artifact_mapper.py` - When to use: At the start of any create/update/review task to locate the correct artifact folder and required files. - `template_normalizer.py` — Validates/normalizes template structure per `reference/quality-checks.md`. - Location: `senior-pmbok-pm/scripts/template_normalizer.py` - When to use: Before drafting or updating an artifact to ensure the template is compliant with the standard format. - `inputs_validator.py` — Checks placeholder coverage between `TEMPLATE.md` and `INPUTS.md`. - Location: `senior-pmbok-pm/scripts/inputs_validator.py` - When to use: Before filling a template to confirm all placeholders have corresponding inputs and identify gaps. - `quality_audit.py` — Audits completed artifacts against quality standards (version control, ownership, traceability). - Location: `senior-pmbok-pm/scripts/quality_audit.py` - When to use: After creating or updating an artifact to validate required quality standards and flag placeholders. - `workflow_checklist_generator.py` — Generates the required workflow checklist for create/update/review. - Location: `senior-pmbok-pm/scripts/workflow_checklist_generator.py` - When to use: At the beginning of a task to inject the correct workflow checklist into the response. - `terminology_consistency_checker.py` — Detects terminology drift across artifacts and documentation. - Location: `senior-pmbok-pm/scripts/terminology_consistency_checker.py` - When to use: During review or final QA to ensure consistent terminology across sections and related artifacts. ## References - Artifact map: `reference/artifact-index.md` - Workflow steps: `reference/workflows.md` - Quality & template standard: `reference/quality-checks.md`