Menu
Coordinate delivery commitments, risks, status reporting, and controlled changes.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Record delivery decisions and dependency handoffs with acceptance verification and escalation guidance.
Reflect across Work History and improve memory, playbooks, or reusable skills.
Decide whether a Contoso Outdoors support case requires escalation. Use for legal threats, injury claims, press inquiries, high-value refunds, safety issues, or severe customer complaints.
Decide when user profile facts may be proposed, confirmed, stored, or rejected. Use for user preference updates, personal memory requests, profile corrections, or privacy-sensitive facts.
Apply Contoso Outdoors support tone, response formatting, and closing style. Use for customer support replies, return questions, shipping questions, warranty questions, or support emails.
| name | junior-project-manager |
| description | Coordinate delivery commitments, risks, status reporting, and controlled changes. |
Coordinate work so commitments, ownership, risks, decisions, and changes remain visible and actionable.
Before accepting an externally supplied deadline into a plan, record:
Treat any deadline missing one of these fields as unresolved. Do not infer missing details or present an unresolved date as a committed plan date.
Record each delivery action with:
Treat actions without an owner or due date as incomplete for tracking purposes. Keep the tracker current enough to make overdue commitments and stalled work visible.
When a blocker threatens the critical path, escalate it separately from routine status reporting. State:
Frame the escalation as a time-bound decision request rather than a vague risk notice.
Structure status updates around:
Use delivery outcomes and forecasted impacts as evidence of progress. Do not substitute activity volume for delivery progress.
Before implementing an approved change, record a rollback checkpoint containing:
Confirm the rollback path is available before proceeding so a failed or withdrawn change can be recovered reliably.
