Menu
Escalate issues to higher authority
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | aget-escalate-issue |
| description | Escalate issues to higher authority |
| archetype | supervisor |
| allowed-tools | ["Read","Glob","Write"] |
Escalate issues to higher authority when they exceed current scope. Creates structured escalation documentation.
When this skill is invoked:
Verify Escalation Needed
Document Context
Identify Target
Create Escalation
| Should Escalate | Should NOT Escalate |
|---|---|
| Exceeds authority | Within authority |
| Cross-portfolio | Single portfolio |
| Policy change | Operational |
| Resource conflict | Local resource |
| Security/compliance | Routine issue |
## Escalation Request
### Issue Summary
| Field | Value |
|-------|-------|
| ID | ESC-[YYYY]-[NNN] |
| From | [Escalating Agent] |
| To | [Target Authority] |
| Date | [YYYY-MM-DD] |
| Urgency | [Low/Medium/High/Critical] |
---
### Issue Description
**Title**: [Brief title]
**Description**: [Full description of the issue]
**Impact**: [Who/what is affected, severity]
---
### Why Escalation Required
**Authority Check**:
- [ ] Issue exceeds my decision authority
- [ ] Requires cross-portfolio coordination
- [ ] Policy/governance decision needed
- [ ] Resource beyond my allocation
**Prior Attempts**:
1. [Attempt 1]: [Result]
2. [Attempt 2]: [Result]
---
### Request
**Decision Needed**: [Specific decision or action requested]
**Options** (if applicable):
1. [Option A]: [Pros/Cons]
2. [Option B]: [Pros/Cons]
**Recommendation**: [If you have one]
---
### Urgency Justification
**Urgency**: [Level]
**Why**: [Justification for urgency level]
**Deadline** (if any): [Date/Time]
---
### Tracking
**Escalation ID**: ESC-[YYYY]-[NNN]
**Status**: Open
**Created**: [Timestamp]
Close a PROJECT_PLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECT_PLAN lifecycle.
Commit a selected candidate goal into a durable, governed Goal artifact. The D71-Strict singular committer of the propose-goals→create-goal verb pair (L1067/L1085). Two-tier (REQ-3): committed goals = a structured section in governance/GOALS.md; aspirational = agent-internal .aget/goals/aspirational.jsonl. Direct authoring of a committed-Goal section is PROHIBITED once this skill is invoked. Implements AGET_GOAL_SPEC v0.2.0 (CAP-GOAL-001..011).
Scaffold approved initiative manifests at planning/initiatives/INIT-*.md. Mirrors /aget-create-project STRICT (D71 Layer 2) — direct Write/Edit to planning/initiatives/ is PROHIBITED once this skill is invoked. Implements SOP_initiative.md (graduated procedure) + future AGET_INITIATIVE_SPEC. Consumes PROPOSAL_init_*.md substrate produced by /aget-propose-initiative.
Create lightweight initiative proposals (PROPOSAL_init_*.md) before full INIT-*.md scaffolding. Follows 'propose -> review -> approve -> create' governance pattern. Advisory enforcement. Implements AGET_INITIATIVE_SPEC v1.0.1 CAP-INIT-PROP-001..012.
Record principal authorization (GO) with Healthy Friction enforcement of the principle-triad (spec+verify-first, coherence-next, evidence-driven); release agent execution within authorized scope. Authorization-only — does not execute the authorized work.
Generate standalone narrative documents from session artifacts, optimized for a target consumption medium (NotebookLM, slides, memo, share-draft). Use when the user says "create briefing", "create a briefing for NotebookLM", "make this listenable", "summarize session for [medium]", "prepare a listen", "brief me on [topic]", or "create a summary I can share".