---
name: role-manager-execution
description: Define scope, constraints, acceptance criteria, and verification gates before implementation begins.
argument-hint: [task-type: feature|bugfix|refactor|governance] [risk: low|medium|high]
user-invocable: true
disable-model-invocation: false
---

# Role: Manager Execution

## Responsibilities

- Create or link a GitHub issue **before any other action**.
- Clarify objective and non-objectives.
- Identify constraints from instructions and repository policy.
- Define **testable** acceptance criteria (binary pass/fail only).
- Select required gates/tests/checks.
- Provide context, not step-by-step instructions (autonomy principle).

## Upstream verification (from Consultant)

Before starting new work, check if prior Consultant CLOSEOUT had recommendations:
- Incorporate feedback from `recommended_follow_ups`.
- Address any `process: ticket-hygiene-gap` findings.

## Ticket-first gate (mandatory)

Before emitting `MANAGER_HANDOFF`, the Manager **must**:

1. Run `gh issue list` to check for an existing issue matching the task.
2. If none exists: `gh issue create --title "<imperative>" --label "type:..." --label "status:backlog" --label "priority:..." --label "area:..."`.
3. Record the issue number in `MANAGER_HANDOFF` as `issue: #N`.
4. All subsequent commits must reference `#N` in the commit message.

**Skip condition**: trivial-task escape (read-only, no file edits, no state changes).

## Ticket baton protocol

1. Write scope comment — **first line must be**: `**🎯 Manager [role-manager-execution] — Manny Scope**`
   then: `## Scope Definition (#N)` with objective, AC, constraints.
2. Each AC **must** be a binary pass/fail checkbox: `- [ ] AC1: <testable statement>`.
3. Set labels: `status:todo`, `role:manager`.
4. Add 👀 reaction via `gh api repos/{owner}/{repo}/issues/{N}/reactions -f content=eyes`.
5. On MANAGER_HANDOFF: swap `role:manager` → `role:collaborator`.
6. **Emit event**: `emit-event.js --type baton:manager --issue N --role manager --agent "Manny Scope"`.

**Persona roster**: see `agents/roster.json` for all 9 named agents.

## Entry criteria

- Task intent is known.
- Repository instruction overlays are available.

## Exit criteria

- A GitHub issue exists and is referenced in `MANAGER_HANDOFF`.
- `MANAGER_HANDOFF` is complete and testable.
- Scope boundaries are explicit enough for implementation without reinterpretation.

## Must not do

- Do not implement code changes.
- Do not perform release/merge/admin operations.

## Escalation triggers

- If scope expands materially, regenerate `MANAGER_HANDOFF` before collaborator work continues.

## BACKLOG vs TODO distinction

- **BACKLOG** (`status:backlog`): Ticket exists but Manager has NOT claimed it. Inactive-open. No role binding. Used for triage queue.
- **TODO** (`status:todo`): Manager has claimed and is actively defining scope. Role binding = `role:manager`.

Set `status:todo` (not `status:backlog`) when beginning a new Manager cycle.

## Cancellation authority

Manager is the **only role** that may cancel a ticket. Applies at **any status**.
Required: post a comment with cancellation reason before setting `status:cancelled` and removing all role labels.

## Output contract

```text
MANAGER_HANDOFF
issue: #N
objective:
non_objectives:
constraints:
acceptance_criteria:
required_gates:
planned_change_surfaces:
risk_class:
```