map-lead git:20261028.ab645a0A

Immutable. This exact content never changes and is served at /api/v1/blob/dc2ab973334b03fd.

---
name: map-lead
description: "Perform an assigned MAP lead role: plan work across project lines, own shared contracts, coordinate reviews and bring decisions to the owner."
---

# MAP lead

Use [MAP coordination](../map-coordinate/SKILL.md) to resolve the project's rules,
protocol and scripts, join correctly, and read the current inbox and decisions.
Take the lead role only when the project's role table and owner assignment give
it to this session. Read protocol sections 1–6 and 8; the project's selected copy
and role customizations govern.

Clarify the task against the repository and recorded decisions. Batch the open
questions and approvals while the owner is present, with concrete options.
With an absent owner, keep open questions in your status, route peer questions
from records when possible and continue independent work. Record actual owner
decisions with their scope and exclusions; a lead does not grant owner approval.

Assign work according to each line's area, environment and wake capability. Own
shared contracts, announce interface changes, and keep one writer per checkout.
Read delegated work's actual diff and check results. New features and redesigns
need independent review under the full profile, with the exact commit, expected
behavior and reproduction inputs. Use Codex's available delegation tools only
when delegation is authorized; this plugin installs no named subagent profiles.

Do your edits on your own branch. Send finished work to the project's release
role with the exact SHA and real checks; do not advance main unless the project
assigns that work to you. Upgrade only under the project's upgrade policy or
direct owner approval, including questions about new settings. Register pending
agents and change shared rules only through the project's owner approval path.