status-report

name	status-report
description	Run the TPG-Scheduler-Codex-Plugin workflow for confirmation-gated Dynamics 365 TPG project status reporting from the repository root plugin entry.

TPG Status Report

Use this root skill entry when the plugin is installed from the repository root. The implementation package, tests, fixtures, and deeper documentation live in plugins/tpg-scheduler-codex-plugin/.

For PMO reporting, the Full Board Pack / Steering Pack, portfolio management packs, the 12-report PMO suite, or DOCX/XLSX management reports, use the pmo-report-suite skill instead.

Operating Rules

• Use the Codex in-app Browser for Dynamics 365 work.
• Read Dataverse data through the authenticated Dynamics browser context as the production path.
• For PMO inputs, call D365 API helpers such as TPGProjectAssist.retrieveProjectIntelligenceFromD365(), retrieveBoardPackFromD365(), retrieveStatusSuggestionReportFromD365(), retrieveMonthlyStatusPlanFromD365(), buildLivePmoControlCenterFromD365(), or retrieveMonthlyPmSelfServiceFlowFromD365(); do not use downloaded exports as the normal path.
• Verify the configured project manager before collecting or staging a status update.
• For monthly runs, prepare one Status Update per active verified project and report month with --monthly-status-plan.
• Use the Status API Max Layer and D365 API Max helpers for automatic status suggestion reports, status history, duplicate checks, idempotency, writeback queues, metadata discovery, permission probes, audit evidence packs, live PMO control center output, Submitted-To resolution, Power BI-ready output, and confirmation-gated Dataverse create plans.
• Use TPG_PLUGIN_SETTINGS for D365 URLs, project metadata, status-update fields, workflow defaults, and safety defaults; avoid scattering literal settings across new code.
• Show project safety level and PMO control findings before collecting or staging a status update.
• When generating intelligence JSON, include and explain maximumUsps if the user asks for USPs, differentiation, PMO/CIO/CEO value, or product positioning.
• When the user asks for PMO-specific value, operational PMO workflows, steering, board packs, audit, or CIO/CEO PMO outcomes, include and explain pmoUsps and boardPack.
• Show logicValidation.assuranceLevel and material Logic Assurance findings before collecting or staging status when intelligence data is available.
• Treat kv as the configured unchanged-status shortcut.
• Never save, submit, send, delete, change ownership, or change CRM state without explicit user confirmation.
• Treat Email Status Update as a separate high-risk setting that must be reviewed before any save.

Local Commands

cd plugins/tpg-scheduler-codex-plugin
npm run status-report:help
node ./scripts/statusbericht.js --intelligence <snapshot.json> --allow-offline-input
node ./scripts/statusbericht.js --board-pack <snapshot.json> --allow-offline-input --docx reports/board-pack.docx --xlsx reports/board-pack.xlsx
node ./scripts/statusbericht.js --monthly-status-plan <snapshot.json> --allow-offline-input --month YYYY-MM --json
node ./scripts/statusbericht.js --pmo-report <snapshot.json> --allow-offline-input --project-status "In Progress"
node ./scripts/statusbericht.js --pmo-report <snapshot.json> --allow-offline-input --docx reports/pmo-status.docx --xlsx reports/pmo-status.xlsx
npm test

Evidence To Show

Before staging any CRM draft, show:

• project identity and current record URL
• project-manager verification result
• safety level and writeback risk
• PMO intervention recommendation
• maximum USP signals when relevant
• PMO USP command queue, evidence ledger, and data gaps when relevant
• Logic Assurance level, evidence trace issues, false-green warnings, kv blockers, and writeback negative findings when relevant
• Board Pack safety, project links, evidence ledger, and data gaps when relevant
• required evidence gaps
• exact status text and email setting that would be staged